Open documentation ↗Overview
Streamline your customer due diligence with Credas' digital identity verification software and AML technology.
Credas API is a security API from credas.co.uk. It needs no API key. It is served over HTTPS. Its OpenAPI description documents 37 endpoints.
At a glance
- Authentication
- No auth
- HTTPS
- Yes
- CORS
- Unknown
- Category
- Security
- Version
- v1
- Endpoints
- 37
- OpenAPI
- Specification ↗
- Spec updated
- 2023-03-06
Endpoints
| Method | Path | What it does |
|---|---|---|
| POST | /api/bank-accounts/verify | Verifies bank account details. |
| POST | /api/companies | Searches for a company based on its Company Number and returns its details. |
| GET | /api/companies/{companyId} | GetCompany |
| POST | /api/credit-status/perform | Check includes identifying bankruptcy, insolvency, CCJ's or Company Directorship. |
| POST | /api/datachecks | Creates new data check against a specified registration. |
| POST | /api/images/id-document | Add an id document image to the specified registration. |
| GET | /api/images/id-document/{registrationId} | Get all id document images associated with a registration. |
| POST | /api/images/liveness | Add a liveness image (UAP) to the specified registration. |
| GET | /api/images/liveness-performed/{registrationId} | Retrieve the liveness performed image associated with a registration. |
| GET | /api/images/liveness/{registrationId} | Retrieve the liveness action image (UAP) associated with a registration. |
| GET | /api/images/scan-report-pdf/{scanId} | Returns a detailed report on the analysis that has taken place of a scanned document |
| POST | /api/images/selfie | Add a selfie image to the registration. |
| GET | /api/images/selfie/{registrationId} | Retrieve the selfie image associated with a registration. |
| POST | /api/property-register | Creates new property registry check against the registration. |
| GET | /api/property-register/{id} | Retrieves property registry check associated with the registration. |
| GET | /api/reg-types | Gets all available RegTypes. |
| POST | /api/registrations | Creates new registration. |
| POST | /api/registrations/instant | Creates new registration record, adds an ID document and optional selfie image in one go. |
| GET | /api/registrations/referenceid/{referenceId}/summary | Finds registrations by the ReferenceId. |
| GET | /api/registrations/regcode/{regCode}/summary | Finds a registration by the RegCode. |
| GET | /api/registrations/search | Gets paged registration list by search criteria or nothing if there are no matching fields. Optional parameters may be appended to the query string. Maximum p |
| GET | /api/registrations/{id}/check-submitted-id-documents | Checks if submitted documents are sufficient to complete registration. |
| PUT | /api/registrations/{id}/contact-details | Updates a registration's contact details. |
| PUT | /api/registrations/{id}/override-check-status | Sets an override for a specific check on the registration. |
| GET | /api/registrations/{id}/pdf-export | Returns PDF export for a given registration. |
| GET | /api/registrations/{id}/pdf-export-sections | Returns a PDF report for a given registration containing specified sections |
| GET | /api/registrations/{id}/pdf-settlement-status | Returns settlement status PDF (Share Code) for a given registration. |
| POST | /api/registrations/{id}/resend-invitation | Resends any invitation for the specified registration. |
| GET | /api/registrations/{id}/settings | Gets registration settings or nothing if there are no settings associated with the registration. |
| PUT | /api/registrations/{id}/settings | Updates registration settings. |
| PUT | /api/registrations/{id}/status | Updates the status of the registration to one specified in the request. |
| GET | /api/registrations/{id}/summary | Finds a registration by the Id. |
| GET | /api/registrations/{id}/supported-id-documents | Get a list of supported id document for the specified registration id. |
| POST | /api/report-view/by-referenceid | Retrieves secure links to registration details pages searching by the Reference Id. |
| POST | /api/report-view/by-registrationid | Retrieves secure link to registration details page searching by the Registration Id. |
| POST | /api/web-verifications/by-referenceid | Retrieves secure links to web verification pages searching by the Reference Id. |
| POST | /api/web-verifications/by-registrationid | Retrieves secure link to web verification page searching by the Registration Id. |
Questions
Does the Credas API API need an API key?
No. The Credas API API can be called without an API key or sign-up, which makes it handy for prototypes and front-end demos.
Does the Credas API API support HTTPS?
Yes, the Credas API API is served over HTTPS.
How many endpoints does the Credas API API have?
Its OpenAPI description lists 37 endpoints in version v1. All of them are shown on this page.
What are alternatives to the Credas API API?
Other Security APIs include Microsoft Security Response Center (MSRC), National Vulnerability Database, Cisco PSIRT openVuln API, Shodan, BitWarden.
Similar security APIs
Compare alternatives →Microsoft Security Response Center (MSRC)
SecurityProgrammatic interfaces to engage with the Microsoft Security Response Center (MSRC)
National Vulnerability Database
SecurityU.S. National Vulnerability Database
Cisco PSIRT openVuln API
SecurityThe Cisco Product Security Incident Response Team (PSIRT) openVuln API is a RESTful API that allows customers to obtain Cisco Security Vulnerability information in different machine-consumable formats. APIs are important for customers because they allow their technical staff and programmers to build tools that help them do their job more effectively (in this case, to keep up with security vulnerability information). For more information about the Cisco PSIRT openVuln API visit https://developer.cisco.com/site/PSIRT/discover/overview For detail steps on how to use the API go to:https://developer.cisco.com/site/PSIRT/get-started/getting-started.gsp This is a beta release of a swagger YAML for the Cisco PSIRT openVuln API To access the API sign in with your Cisco CCO account at http://apiconsole.cisco.com and register an application to recieve a client_id and a client_secret You can then get your token using curl or any other method you prefer. 'curl -s -k -H "Content-Type: application/x-www-form-urlencoded" -X POST -d "client_id=<your_client_id>" -d "client_secret=<your_client_secret>" -d "grant_type=client_credentials" https://cloudsso.cisco.com/as/token.oauth2' You will receive an access token as demonstrated in the following example: '{"access_token":"I7omWtBDAieSiUX3shOxNJfuy4J6","token_type":"Bearer","expires_in":3599}' In Swagger, click on Change Authentication enter the text "I7omWtBDAieSiUX3shOxNJfuy4J6" (which is the token you received) then click on "Try this operation"
Shodan
SecuritySearch engine for Internet connected devices
BitWarden
SecurityBest open-source password manager
HaveIBeenPwned
SecurityPasswords which have previously been exposed in data breaches
Listed from APIs.guru (CC0).