Plan an EntityLocker Requester API Integration
Prepare a version register and test plan for an EntityLocker requester integration. Confirm the applicable contract before wiring organisation document access.
Confirm the EntityLocker contract before choosing endpoints or writing an executable example. Record the revision the provider assigns to your application and environment.
The official resources page labels the linked requester download August 2026. The downloaded PDF identifies itself as version 1.0, October 2024. Use the document contents and provider confirmation to resolve that difference for your project. EntityLocker resources EntityLocker requester specification
Create a version register
| Item | What to record |
|---|---|
| Listing | Resource page label and retrieval date |
| Download | Document title, revision, and date printed inside the file |
| Approved contract | Provider-confirmed revision and application |
| Configuration | Exact environment, client, redirect, and permission set |
| Compatibility | Date and result of a test with approved credentials |
| Owner | Person who reviews changes and renews approval |
Keep the register with your engineering notes. If a partner portal gives your organisation a different document, record which one the provider tells you to use.
Plan the request journey
The linked specification describes OAuth authorization, entity and user information, document retrieval, and revocation. Review those sections in the confirmed contract before making assumptions about the available operations. EntityLocker requester specification
Start your design with a signed-in representative. Check their local authority for the organisation. Begin a provider request for the required documents. Verify the return binding and permitted access. Save the outcome under the correct entity.
For a synthetic test, a representative starts the request for Company A. The browser returns while Company B is selected in your app. Resolve the result against the original server-side attempt and require the appropriate authority before any access.
Confirm compatibility in the approved environment
- Check the exact authorization and token endpoints.
- Verify the callback and code exchange.
- Check the returned organisation identifier and permission shape.
- Retrieve only a supported document under the approved grant.
- Exercise cancellation and the approved cleanup route.
- Record the results with the contract revision.
Use synthetic responses for local development. Label the results as simulations until you have compatibility evidence from the approved environment.
Keep the application decision separate
The provider can return organisation and user details. Your application decides whether that person can perform the intended action for the organisation. Business onboarding and representative authority.
Review the application boundary with NamoID
NamoID engineers can help review the callback and account design around an EntityLocker workflow. Share your confirmed specification revision, stack, and a synthetic trace in Slack. Message the NamoID team in Slack