Automate Credas

What HumDay can do in Credas

19 documented operations change something in Credas.

• POSTCreates new registration record, adds an ID document and optional selfie image in one go./api/registrations/instant
• POSTCreates new data check against a specified registration./api/datachecks
• POSTCreates new registration./api/registrations
• POSTCreates new property registry check against the registration./api/property-register
• POSTAdd an id document image to the specified registration./api/images/id-document
• POSTAdd a selfie image to the registration./api/images/selfie
• POSTAdd a liveness image (UAP) to the specified registration./api/images/liveness
• POSTRetrieves secure link to registration details page searching by the Registration Id./api/report-view/by-registrationid
• POSTRetrieves secure link to web verification page searching by the Registration Id./api/web-verifications/by-registrationid
• POSTSearches for a company based on its Company Number and returns its details./api/companies
• PUTUpdates a registration's contact details./api/registrations/{id}/contact-details
• POSTVerifies bank account details./api/bank-accounts/verify
• POSTCheck includes identifying bankruptcy, insolvency, CCJ's or Company Directorship./api/credit-status/perform
• POSTRetrieves secure links to registration details pages searching by the Reference Id./api/report-view/by-referenceid
• POSTRetrieves secure links to web verification pages searching by the Reference Id./api/web-verifications/by-referenceid
• PUTUpdates the status of the registration to one specified in the request./api/registrations/{id}/status
• PUTUpdates registration settings./api/registrations/{id}/settings
• POSTResends any invitation for the specified registration./api/registrations/{id}/resend-invitation
• PUTSets an override for a specific check on the registration./api/registrations/{id}/override-check-status

What HumDay can read from Credas

These are the operations a schedule or a trigger can watch.

• GETGets paged registration list by search criteria or nothing if there are no matching fields./api/registrations/search
• GETGet a list of supported id document for the specified registration id./api/registrations/{id}/supported-id-documents
• GETGets all available RegTypes./api/reg-types
• GETReturns a detailed report on the analysis that has taken place of a scanned document/api/images/scan-report-pdf/{scanId}
• GETGet all id document images associated with a registration./api/images/id-document/{registrationId}
• GETReturns settlement status PDF (Share Code) for a given registration./api/registrations/{id}/pdf-settlement-status
• GETRetrieves property registry check associated with the registration./api/property-register/{id}
• GETFinds a registration by the Id./api/registrations/{id}/summary
• GETGets registration settings or nothing if there are no settings associated with the registration./api/registrations/{id}/settings
• GETReturns PDF export for a given registration./api/registrations/{id}/pdf-export
• GETRetrieve the selfie image associated with a registration./api/images/selfie/{registrationId}
• GETRetrieve the liveness action image (UAP) associated with a registration./api/images/liveness/{registrationId}
• GETReturns a PDF report for a given registration containing specified sections/api/registrations/{id}/pdf-export-sections
• GETRetrieve the liveness performed image associated with a registration./api/images/liveness-performed/{registrationId}
• GETChecks if submitted documents are sufficient to complete registration./api/registrations/{id}/check-submitted-id-documents
• GETFinds a registration by the RegCode./api/registrations/regcode/{regCode}/summary
• GETFinds registrations by the ReferenceId./api/registrations/referenceid/{referenceId}/summary
• GETRead companyId/api/companies/{companyId}

How automating Credas works

1. Describe the outcome. Say what you want to happen, in your own words. No node graphs, no field mapping.
2. Approve the contract. HumDay writes down exactly what it will do, what it will touch, and what it will never do. You approve it before anything is built.
3. See it proven. The program runs and shows you the result before it is allowed near your live Credas account.
4. Grant access, then go live. You approve the specific Credas operations it may use — and only those.

Automate Credas with these

• Cloudflare3122 operations
• IX API IX78 operations
• N Auth nextAuth55 operations
• Conjur41 operations
• Cisco PSIRT openVuln19 operations
• Users (Okta )19 operations
• 1Password Connect15 operations
• CyCAT.org14 operations
• Swagger for Patrowl Engines14 operations
• Appspot Authentiq12 operations
• Testfire AltoroJ12 operations
• hashlookup CIRCL11 operations

Categories

• Security

Questions about Credas automation

Can HumDay connect to Credas?

Yes. HumDay reads Credas's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 37 operations are documented.

Do I need to write code to automate Credas?

No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a test run before anything touches your Credas account.

What can HumDay do in Credas?

19 of the 37 documented operations change something in Credas, and 18 read from it. HumDay only ever uses the specific operations your approved contract needs.

Is my Credas account safe?

Your credentials are stored encrypted and are never shown in chat, code, or logs. Every run is limited to the operations you explicitly approved, and anything that writes to Credas is held behind that approval.

Where this came from

The operations above are read from a published API description for Credas at pi-api.credas.co.uk/swagger/v1/swagger.json. Descriptions are the provider’s own words, not ours. Last published 2023-03-06.