Redirect user

Data submission

Submit user data to SEEK Pass using the correct endpoint based on credential type. For example, for the Education credential type the endpoint to call is: /api/partner/v1/add/education.json:

export CREDENTIAL_TYPE=education

curl -L $SEEK_PASS_URL/api/partner/v1/add/$CREDENTIAL_TYPE.json \
-H 'Content-Type: application/json' \
-H "Authorization: Bearer $ACCESS_TOKEN" \
--data '<PAYLOAD FROM STEP 1>'

Response codes:

201 Created: Successful request

{
    "redirect_uri": "https://app.seekpass-staging.com/partner/add/education#clientId=730845ab-0a0d-4f4d-9c98-d871755d3ce9&documentType=open_cert&content=d8a8eb57-c64f-4fc1-b362-b8df28fbf0a3"
}

Note: CURL returns invalid \u0026 instead of &. Please replace \u0026 with & in the redirect URL. Other clients should not have this issue.

Batch API

Note: The credential batch feature is currently under development. Updates will be provided as soon as it becomes available.

The Batch API allows you to submit multiple credentials in a single API request. This endpoint is able to streamline the user experience of adding multiple credentials at once. This can be used to handle:

Multiple of a single type of credential (e.g. 2x Education Qualifications)
Multiple of multiple types of credentials (e.g. 1x Digital Identity, 2x Education Qualifications and 5x Learning and Development Credentials)

curl -L $SEEK_PASS_URL/api/partner/v1/add/batch.json \
-H 'Content-Type: application/json' \
-H "Authorization: Bearer $ACCESS_TOKEN" \
--data '<BATCH PAYLOAD>'

Response codes:

201 Created: Successful request

{
    "redirect_uri": "https://app.seekpass-staging.com/partner/add/batch#clientId=730845ab-0a0d-4f4d-9c98-d871755d3ce9&content=b4ce8d4e-f293-4492-9d7a-4210bdbe099e"
}

Behaviour

If the same id is used within 48 hours, the same redirect_uri will be returned.
After 48 hours, the old data is deleted. A new POST request with the same id will save the data with a different SEEK Pass ID and return a new redirect_uri.
Once the user clicks the link and logs into the system, the data is associated only with them.
Even if the user has not accepted consent, the data is associated, and the redirect_uri will prompt them to accept consent.
Once consent is accepted, subsequent requests will return the same URL to view the credential submission.
In line with our data protection policies, if a user goes through the Add to SEEK Pass flow, but does not download and sign into the mobile application within 48 hrs of completing the flow, the user's documents will be securely deleted.

Once a user clicks the link and logs into the system, the data is associated only with them. If another user attempts to use the same link, they will be redirected to an error page.

Redirect to SEEK Pass

The redirect_uri obtained in the previous step must be used to redirect users to the SEEK Pass application.

URL format

The redirect URL is generated with this format:

Path: /partner/add/[CREDENTIAL TYPE]
- Examples:
  - For Education: /partner/add/education
  - For English proficiency: /partner/add/englishProficiency
  - For Microcredential: /partner/add/microcredential
  - For Batch: /partner/add/batch
- For batch microcredentials: /partner/add/batch/microcredential
Host:
- Production: https://app.seekpass.co
- Staging: https://app.seekpass-staging.com
Hash: the parameters below, encoded as URL query parameters
- clientId: The partner's OAuth client ID
- documentType: The expected document type
- content: The SEEK Pass request ID

Previous: Right to Work

Next: Check submission status