Oracle CRM On Demand REST API Developer's Guide > Getting Started with the Oracle CRM On Demand REST API >

About Oracle CRM On Demand REST API Authentication

The Oracle CRM On Demand REST API uses Oracle CRM On Demand authentication. To use the Oracle CRM On Demand REST API with Oracle CRM On Demand, you must have a valid Oracle CRM On Demand user account to establish a secure session with the Oracle CRM On Demand server. There are several different ways in which Oracle CRM On Demand server sessions can be established and maintained:

• You can log into the Oracle CRM On Demand server through the Oracle CRM On Demand user interface. You must be successfully signed in to Oracle CRM On Demand to send REST API requests and receive REST API responses. If you are not signed in to Oracle CRM On Demand, and if you try to send a REST API request, then you will receive an HTTP 403 forbidden status code. For more information about HTTP status codes, see Standard HTTP Status Codes.
• You can use the Oracle CRM On Demand REST API connection request to establish a session with the Oracle CRM On Demand server using a JSESSIONID cookie. For more information about using the Oracle CRM On Demand REST API connection request to establish an Oracle CRM On Demand server session, see Login with Oracle CRM On Demand REST API.
• You can use the Oracle CRM On Demand REST API and your SSO ID URL parameter to log into the Oracle CRM On Demand server. For more information regarding SSO, Using SSO with the Oracle CRM On Demand REST API.

If authentication is unsuccessful, the Oracle CRM On Demand server returns an HTTP 401 unauthorized status code and you are prompted to authenticate again. If the Oracle CRM On Demand server returns an HTTP 302 found code, the Oracle CRM On Demand checks the login server to confirm if the user is authenticated. If you are authenticated, then you are redirected to the correct URL. For more information about HTTP status codes, see Standard HTTP Status Codes.