Versions Compared
Version | Old Version 4 | New Version 5 |
---|---|---|
Changes made by | ||
Saved on |
Key
- This line was added.
- This line was removed.
- Formatting was changed.
This page collects basic reference material about the Scholar Snapp API
Primary API Endpoints
See the API Overview for context about how each endpoint is used.
URL | Endpoint |
---|---|
OAuth Authorization | https://auth.scholarsnapp.org/oauth/Authorize |
OAuth Token | https://auth.scholarsnapp.org/oauth/Token |
Profile | https://auth.scholarsnapp.org/api/profile/snappfile?version=4 |
HTTP Status Codes
The following is a summary of HTTP status codes and a brief description.
Code | Description |
---|---|
200 - OK | GET, POST:Â Request was successful. |
304 - Not Modified | GET: Client should use cached resource. |
400 - Bad Request | GET: The user authenticated successfully, but the user has no Snapp Profile. POST: The file was received, but does not pass validation against the Snapp Profile specification. |
401 - Unauthorized | GET, POST: Authorization code or bearer token is invalid. |
404 - Not Found | GET, POST: API URL requested does not exist. |
500 - Internal Server Error | GET, POST: Server-side processing error. |
503 - Service Unavailable | GET, POST: Service is down for maintenance. The Snapp platform host will respond with this status for legitimate maintenance issues such as when the internal network, platform, or other component is down for maintenance. The same status is used for other conditions such as a request timeout. Since the same error is returned for both transient and non-transient conditions, contact Scholar Snapp support for investigation and resolution if a 503 error persists. |
Include Page | ||||
---|---|---|---|---|
|