CrashLog accepts notifications over HTTP/S to stdin.crashlog.io
along with an api_key
and payload
The API key is a 32 character secure random string found on the project configuration page within your CrashLog account.
It should be sent along with the payload as a standard HTTP param with the key auth_token
All notifications should be sent to stdin.crashlog.io/notify
over either plain HTTP or HTTPS to port 443.
You can see the notification payload example below, but here are the basics:
The payload can contain multiple interfaces, of which only 2 are required:
- notifier (required)
- event (required)
- backtrace
- environment
- context
A successfully lodged exception will return a hash like:
"{"location_id": "<128bit UUID>"}
location_id
can be used to generate a URL to link directly to the exception or fetch information about it from the CrashLog public API.
Generating URLs
The standard location for locating exceptions within the CrashLog UI is http://crashlog.io/locate/:location_id
This will either return 404
if the exception has not yet been loaded (< T+1 second) or 301
with a redirection to the actual error page.
Fetching API data
You can fetch a JSON representation of the exception using the public API endpoints and your API key (found under your account settings page)
GET https://crashlog.io/api/locate/:location_id