Skip to content
AfterLib API

Request logs

The Developer Portal shows recent public API requests for the current member account.

Request history is useful for:

  • Confirming which key made a request.
  • Seeing the endpoint, status, operation, and credit charge.
  • Debugging validation errors and exhausted credit responses.
  • Auditing collection item reads and writes.

Every response includes X-Afterlib-Request-Id. Error responses also include the same value as error.requestId. Keep that ID when comparing a client-side failure with the request history in the Developer Portal.

AfterLib also records public API activity internally so the team can monitor API behavior, investigate abuse, and support members.