# Find one Request Log `GET /v2/logs/{id}` Core API v2, Logs. Retrieve a Request Log by its ID. Each call is itself recorded as a Request Log, without a response body. **Authentication:** Send `Authorization: Bearer `. To authenticate, generate a Secret API Key from your ODUS Dashboard and include it in the `Authorization` header as follows: `Authorization: Bearer ` ## Parameters ### Path parameters - `id` (string, required) ## Responses ### `200` OK Type: object (RequestLogDTO). - `createdAt` (string (date-time), required): The date and time when the entity was created. Example: `2024-02-18T12:00:00Z`. - `updatedAt` (string (date-time), required, nullable): The date and time when the entity was last updated. Example: `2024-02-21T12:15:00Z`. - `metadata` (map of string to string, nullable): Metadata used by merchants to store additional information about the entity. - `id` (string, required): The unique identifier of the request log entry. Example: `req_log_2QC7PqoUeOxQEWscJJt6B3PkvyL`. - `requestId` (string, required): Unique request identifier for correlating log entries. Example: `abc123`. - `url` (string, required): The URL path of the API request. Example: `/api/payments`. - `method` (string, required): HTTP method of the request. Example: `POST`. - `clientIp` (string, required, nullable): IP address of the client that made the request. Example: `192.168.1.1`. - `userAgent` (string, required, nullable): User-Agent header from the client request. Example: `Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7)`. - `requestHeaders` (object, required, nullable): HTTP request headers captured for this log entry. - `requestBody` (object, required, nullable): The request body payload. May be redacted for PCI compliance. - `responseBody` (object, required, nullable): The response body payload. May be redacted for PCI compliance. - `statusCode` (number, required, nullable): HTTP response status code. Example: `200`. - `initiator` (string, required, nullable): The type of access key used to make the request. - `credentialId` (string, required, nullable): The ID of the credential that authenticated the request. For a key, this is the key's `id`. For a request made from the Dashboard, it is the ID of the signed-in user or of their session. `null` when no credential can be identified: the request carried none, or the entry was recorded before this field was introduced. Example: `skey_2R6lBd1IxNUPqtsQLcJU2PFtyAD`. - `rejectionReason` (string, required, nullable): Why the request was refused because of its credential. `invalid_credential`: the key or session was not accepted, for example because it was deleted, deactivated or has expired. `account_not_entitled`: the credential is valid, but the account does not have access to the API. `null` on every other entry. One of `invalid_credential`, `account_not_entitled`. Example: `invalid_credential`. ### `202` The merchant is entitled but its environment is not provisioned yet. Provisioning has been kicked off (exactly once) and is in progress; retry the request — it succeeds once the environment is ready. Returned only for identity-token (dashboard) requests bound to a merchant, not for secret-key API calls; any such endpoint can return it while provisioning is underway. Type: object (ProvisioningInProgress). - `status` (string, required): Signals the merchant environment is still being provisioned. One of `provisioning`. - `merchantAccountId` (string, required): The merchant account whose environment is being provisioned. Example: `dAI3aa87ROOeupeBCjNSKCOBOisBCYjB`. ### Errors - `400`: The request was rejected. `type` is `invalid_request_error` when the request itself is at fault — `errors` then lists every problem found, with field-attributable entries prefixed by the field’s path; or `invalid_state_error` when the request was well-formed but the resource is not in a state that allows it. - `401`: No API key was supplied, or the key is not valid. `type` is `authentication_error`. - `403`: The API key is valid but lacks the permission this operation requires. `type` is `permission_error`. - `404`: No resource exists with the requested identifier. `type` is `not_found_error`. - `429`: Too many requests. A limit applies per operation; requests to other operations are unaffected. `type` is `rate_limit_error`. Use the `Retry-After-global` header to know when to retry. - `500`: The request could not be completed because of an unexpected error. `type` is `api_error`. - `503`: The request could not be served right now: the API is temporarily at capacity, or a dependency needed to authorize the request is unavailable — the auth service that verifies credentials, or the entitlement lookup behind it. `type` is `api_error`. It is raised before the operation runs, so the request had no effect, and unlike a plain 500 the condition is transient: retry with backoff. - `504`: The request exceeded the processing time limit and was abandoned. `type` is `api_error` and `code` is `timeout` — unlike a plain 500 the request may still have taken effect, so retry with the same idempotency key rather than blindly. Every error response has the same body: see [Errors](https://docs.odus.com/docs/guides/api-features/errors.md). --- Generated from the Core API v2 OpenAPI document, https://api.odus.com/openapi.v2.json. Interactive page: https://docs.odus.com/docs/api/core/v2/request-log-controller-find-one