Finds registrations by the ReferenceId in Credas
A documented Credas operation that only reads, so it can watch for changes without altering anything. Describe what you want to happen and HumDay builds it.
What this operation does
Finds registrations by the ReferenceId.
- GETReads data · Registrations
/api/registrations/referenceid/{referenceId}/summary
How HumDay uses it
- You describe the outcome. Not this operation by name — what you want to happen. HumDay works out which operations it needs.
- The contract names it. Before anything is built, you see exactly which Credas operations the program may use, and this is one of them.
- You approve access. Read-only access is still yours to grant, and still limited to what the contract needs.
Other Credas operations
- Creates new registration recordPOST · changes data
- Creates new data check against a specified registrationPOST · changes data
- Creates new registrationPOST · changes data
- Creates new property registry check against the registrationPOST · changes data
- Add an id document image to the specified registrationPOST · changes data
- Add a selfie image to the registrationPOST · changes data
- Add a liveness image (UAP) to the specified registrationPOST · changes data
- Retrieves secure linkPOST · changes data
Questions
- Can HumDay finds registrations by the referenceid in Credas?
- Yes. This operation is published in Credas's own API description, so HumDay can use it without a hand-built connector — once you have approved it for your automation.
- Does this change anything in my Credas account?
- No. This is a read-only operation, so it can be used to watch for changes or fetch data without altering anything in Credas.
- Do I need to write code?
- No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a proof run before anything touches your Credas account.
Where this came from
Read from a published API description for Credas at pi-api.credas.co.uk/swagger/v1/swagger.json. The description above is the provider’s own wording, not ours. Last published 2023-03-06.