Singpass Developer Docs
Legacy Myinfo v3/v4
Legacy Myinfo v3/v4
  • Legacy Myinfo v3/v4
  • Data Catalog
  • Key Principles
  • Technical Specifications
    • Myinfo v4
      • Difference between v3 and v4
      • Technical Guidelines
      • Technical Concepts
        • OAuth 2.1 Concepts
        • Proof of Key Code Exchange (PKCE)
        • JSON Web Token (JWT)
        • Client Assertions
        • JSON Web Key Store (JWKS)
        • Demonstration of Proof-of-Possession (DPoP)
      • API Specifications
      • Tutorials
        • Tutorial 1: Myinfo Person sample Data
        • Tutorial 2: End-to-end Integration with Myinfo v4 APIs
      • Resources
        • Myinfo Connectors
        • Error Codes
      • FAQ
    • Myinfo v3
      • Technical Guidelines
      • API Specifications
      • Latest X.509 Public Key Certificate
      • Tutorials
        • Tutorial 1: Basic Person API
        • Tutorial 2: Using OAuth2
        • Tutorial 3: Implementing PKI Digital Signature
      • Resources
        • Myinfo Connectors
        • Error Codes
      • FAQ
Powered by GitBook
On this page

Was this helpful?

  1. Technical Specifications
  2. Myinfo v3
  3. Resources

Error Codes

Here are some of the error codes you might encounter:

Error Code
API
Reason

302

Authorise

Possible to have the following error codes in the 'error' attribute.

  • 500: Unknown or other server side errors

  • 503: Myinfo under maintenance

  • access_denied: When user did not give consent

400

Token

Same authcode in the body is being re-used.

Authcode error - missing, invalid, expired, revoked.

401

Token

No security header given

Invalid App ID used. Digital service is not registered with Myinfo

The timestamp of server is not synchronised. Check timestamp of server

The value of the nonce in the authorisation header was deemed to be repeated. Check that the nonce is not re-used

Ensure HTTP 'Authorization' header to be 'PKI_SIGN'

Person

No security header given

Invalid App ID used. Digital service is not registered with Myinfo

The timestamp of server is not synchronised. Check timestamp of server

The value of the nonce in the authorisation header was deemed to be repeated. Check that the nonce is not re-used

Ensure HTTP 'Authorization' header to be 'PKI_SIGN'

The requested UIN/FIN does not match the UIN/FIN of the person who logged in

Requested attributes do not match the attributes consented by person

403

Person

Requested attributes does not match the attributes consented by person. This happens if the list of attributes in your request are different from the attributes specified when calling the token API.

Incorrect API URL used

Digital service is not registered with Myinfo

Request contains attributes not allowable for the digital service

404

Token

Incorrect API URL used.

Same authcode in the body is being re-used.

Person

Incorrect API URL used.

UIN/FIN has a Singpass account, but does not have a Myinfo profile

500

Token

Unexpected error. Check response body for actual error.

Person

Unexpected error. Check response body for actual error.

PreviousMyinfo ConnectorsNextFAQ

Last updated 1 month ago

Was this helpful?