}' PUT /references/904800000 HTTP / 1.1 Authorization : Token reh8inj33o3algd2tpi6tkcnrqf8rjj2 Accept : application/2+json Content-Type : application/json URL Parameters Parameter H "Authorization: Token reh8inj33o3algd2tpi6tkcnrqf8rjj2" \
Proxie pay update#
References Create or Update ReferenceĬreating/Updating a reference with Id 904800000 and setting the amount, date limit and custom_fields. Each element consists of a set of name/value pairs.
An element resource represents an individual member of a collection. A collection represents the set of all resources of a particular type (such as "references" or "payments").
The resources are Collections or Elements. You can read more about the Payment Webhook below. ProxyPay can also POST data to your application when Payment events occur. The JSON Response includes a list of human readable descriptions of the errors with the following structure: Name Please try again later.Īny invalid input parameter will cause a 400 - Bad Request response.
Proxie pay Offline#
Service Unavailable – We're temporarily offline for maintenance. Internal Server Error – We had a problem with our server. Too Many Requests – You've making too many requests to the API.
Not Acceptable – You requested a format that isn't supported. Method Not Allowed – You tried to access a resource with an invalid method. Not Found – The specified resource could not be found. Make sure you keep your API Key a secret! You authenticate to the ProxyPay API by providing your API Key in the Authorization header of every request:Īll API requests must be made over HTTPS. Make sure to replace reh8inj33o3algd2tpi6tkcnrqf8rjj2 in the example with your own API Key. H 'Content-Type: application/json' PUT / HTTP / 1.1 Authorization : Token reh8inj33o3algd2tpi6tkcnrqf8rjj2 Accept : application/2+json Content-Type : application/json H 'Authorization: Token reh8inj33o3algd2tpi6tkcnrqf8rjj2' \ To authenticate, provide the API Key in the request header: curl "" \ We encourage you to explicitly lock the client application to a version by including the Accept header in all requests:Īccept: application/2+json Authentication H 'Content-Type: application/json' PUT / HTTP / 1.1 Accept : application/2+json Content-Type : application/jsonīy default, all requests receive the latest version of the API. The Content-Type header must be set in all requests that include a JSON body:Ĭontent-Type: application/json Endpoints Environment H 'Content-Type: application/json' PUT / HTTP / 1.1 Content-Type : application/jsonĪll request bodies should have content type application/json and be valid JSON. The following table shows API versions currently supported: API Version The current ProxyPay REST API integration version is v2. JSON will be returned in all responses from the API, including errors. We use built-in HTTP features, like HTTP authentication and HTTP verbs, which can be understood by off-the-shelf HTTP clients. The ProxyPay API is organized around REST. You have endpoints to generate numeric references for payments and to receive notification of payments when they occur. This API allows developers to easily integrate with Multicaixa to accept payments.