Enter your payin transactionId and get the details
Title | Payin from bitcoin |
---|---|
Environment |
TEST: https://test.bitload4u.com PROD: https://api.bitload4u.com |
URL |
The URL structure /payin/:transactionId
|
Method |
The request type GET
|
Headers |
Send this headers :{ secret_id : [string] } |
Success callback Response |
Example: Code: 200 Content: { "code": 200, "status": "Success", "message": "Transaction details successfully get", "response": { "status": "new" | "paid" | "confirmed" | "complete" | "expired" | "invalid", "btcPrice": "0.016963", "createdDate": 1500112116000, "expirationTime": 1500113015000, "currentTime": 1500112116000, "btcPaid": "0.000000", "btcDue": "0.016975" } } |
Error Response |
Most endpoints will have many ways they can fail. From unauthorized access, to wrongful parameters etc. All of those should be listed here. It might seem repetitive, but it helps prevent assumptions from being made where they shouldn’t be. Example: Code: 401 Unauthorized Content: { "code": 401, "status": "Error", "message": "Authentication Error. secret_id is invalid" } OR Code: 404 Transaction not found Content: { "code": 404, "status": "Error", "message": "Transaction not found" } |
Sample Call |
Just a sample call to endpoint in a runnable format ($.ajax call or a curl request) – this makes life easier and more predictable.
|