You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
| ?token= | When fetching an invoice via the `merchant` or the `pos`facade, pass the API token as a URL parameter - the same token used to create the invoice in the first place. |`string`|**Mandatory**|
657
+
| ?token= | When fetching an invoice via the `merchant`facade, pass the API token as a URL parameter - the same token used to create the invoice in the first place. |`string`|**Mandatory**|
658
658
659
659
**Headers**
660
660
661
661
| Fields | Description | Presence |
662
662
| --- | --- | :---: |
663
663
| X-Accept-Version | Must be set to `2.0.0` for requests to the BitPay API. |**Mandatory**|
664
664
| Content-Type | must be set to `application/json` for requests to the BitPay API. |**Mandatory**|
665
-
| X-Identity | the hexadecimal public key generated from the client private key. This header is required when using tokens with higher privileges (`merchant` facade). When using standard `pos` facade token directly from the [BitPay dashboard](https://test.bitpay.com/dashboard/merchant/api-tokens) (with `"Require Authentication"` disabled), this header is not needed. |**Mandatory**|
666
-
| X-Signature | header is the ECDSA signature of the full request URL concatenated with the request body, signed with your private key. This header is required when using tokens with higher privileges (`merchant` facade). When using standard `pos` facade token directly from the [BitPay dashboard](https://test.bitpay.com/dashboard/merchant/api-tokens) (with `"Require Authentication"` disabled), this header is not needed. |**Mandatory**|
665
+
| X-Identity | the hexadecimal public key generated from the client private key. This header is required when using tokens with higher privileges (`merchant` facade). When using standard `merchant` facade token directly from the [BitPay dashboard](https://test.bitpay.com/dashboard/merchant/api-tokens) (with `"Require Authentication"` disabled), this header is not needed. |**Mandatory**|
666
+
| X-Signature | header is the ECDSA signature of the full request URL concatenated with the request body, signed with your private key. This header is required when using tokens with higher privileges (`merchant` facade). When using standard `merchant` facade token directly from the [BitPay dashboard](https://test.bitpay.com/dashboard/merchant/api-tokens) (with `"Require Authentication"` disabled), this header is not needed. |**Mandatory**|
667
667
668
668
669
669
To get the generated invoice details, pass the Invoice Id with URL parameter
| ?token= | When fetching an invoice via the `merchant` facade, pass the API token as a URL parameter - the same token used to create the invoice in the first place. |`string`|**Mandatory**|
690
+
691
+
**Headers**
692
+
693
+
| Fields | Description | Presence |
694
+
| --- | --- | :---: |
695
+
| X-Accept-Version | Must be set to `2.0.0` for requests to the BitPay API. |**Mandatory**|
696
+
| Content-Type | must be set to `application/json` for requests to the BitPay API. |**Mandatory**|
697
+
| X-Identity | the hexadecimal public key generated from the client private key. This header is required when using tokens with higher privileges (`merchant` facade). When using standard `merchant` facade token directly from the [BitPay dashboard](https://test.bitpay.com/dashboard/merchant/api-tokens) (with `"Require Authentication"` disabled), this header is not needed. |**Mandatory**|
698
+
| X-Signature | header is the ECDSA signature of the full request URL concatenated with the request body, signed with your private key. This header is required when using tokens with higher privileges (`merchant` facade). When using standard `merchant` facade token directly from the [BitPay dashboard](https://test.bitpay.com/dashboard/merchant/api-tokens) (with `"Require Authentication"` disabled), this header is not needed. |**Mandatory**|
699
+
700
+
701
+
To get the generated invoice details, pass the guid with URL parameter
* Retrieve a BitPay invoice by invoice id using the specified facade. The client must have been previously authorized for the specified facade (the public facade requires no authorization).
304
+
* Retrieve a BitPay invoice by invoice id using the specified facade. The client must have been previously authorized for the specified facade.
305
305
*
306
306
* @param invoiceId The id of the invoice to retrieve.
0 commit comments