---
title: "Get invoice"
method: GET
path: "/v1/invoices/{access_key}"
tags: ["Invoices"]
---

# Get invoice

`GET /v1/invoices/{access_key}`

Get and validate invoice given access key in path. The access key is created via the [Register receivable](create-receivable) endpoint.

Pismo works with a third-party (B3) who registers the invoices.

This endpoint generates 4 possible events:

1. Request to third-party fails - <a href="https://developers.pismo.io/events/docs/depositary-invoice-validation-request-failure-1" target="_blank">invoice_validation_request_failure-1</a>
2. Request to third-party succeeds - <a href="https://developers.pismo.io/events/docs/depositary-invoice-validation-request-success-1" target="_blank">invoice_validation_request_success-1</a>
3. Third-party validation fails- <a href="https://developers.pismo.io/events/docs/depositary-invoice-validation-failure-1" target="_blank">invoice_validation_failure-1</a>
4. Third-party validation succeeds - <a href="https://developers.pismo.io/events/docs/depositary-invoice-validation-success-1" target="_blank">invoice_validation_success-1</a>

## Path parameters

- `access_key` string, required

## Response `202`

Success message is sent to the client while an invoice validation is processed asynchronously,

- GetInvoiceResponse
  - `access_key` string — Client-generated identifier. This field is used for the [Get invoice](https://developers.pismo.io/pismo-docs/reference/findbyaccesskey) endpoint.
  - `message` string — Message

## Other responses

- `400` — Bad request
- `401` — Access token is missing or invalid
- `500` — Internal server error

---

[API](https://skmtc.net/pismo/apis/platform-authentication.md) · [All operations](https://skmtc.net/pismo/apis/platform-authentication/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/pismo/platform-authentication/revisions/935b62e16de4/schema)