Allow user to get their invoice by invoice number

Changelogs

Version	Date	Changes by	Description of change
V1.0	24 Oct 2024	Tam Tran	Added Table of Contents. Added Changelogs.

Order Resource

Id guid

Id Uniquie Identifier

Content text

File’s uri

Name text

File Name

Type object

Value: Value of Enum
Description: Description of Enum

DocType (AggregatedDocument, FeeCodeDocument, ….)

CreatedTime datetime

Created Time

{
    "Id": "cf318b17-a029-4ce3-fac1-08dc124b675c",
    "Content": "https://dev.file.rehash.redex.eco/58e1b892-ae33-4fad-922e-08dc124b5b70/1704939423946_2024-01-10_170853.png",
    "Name": "2024-01-10_170853.png",
    "Type": {
        "Value": "BankStatement",
        "Description": "Bank statement"
    },
    "CreatedTime": "2024-01-11T02:17:04.61"
}

API Definition

GET public/v2/profile/documents

Request

Headers

Content-Type	`application/json`
Authorization	`Bearer {{access_token}}`

Query Parameters

curl --location 'https://uat-api.redex.eco/public/v2/profile/documents' \
--header 'accept: application/json' \
--header 'Authorization: Bearer {{access_token}}'

Response

Response Body

Data object collection - Order Resource

A collection of objects - Order Resource

Errors list of error objects

Please see "Getting Started - #Error Object" for more details

请查看Getting Started - #Error Object以获得更多信息。

Meta pagination resource

Return Pagination Resource

返回分页信息

StatusCode integer

Http Status codes standard. Example 200, 201, 400, 422.

http状态码，如200，201，400, 422

Message text

Response message: Success or error message.

返回成功或错误的信息。

200 Success

{
    "Data": [
        {
            "Id": "cf318b17-a029-4ce3-fac1-08dc124b675c",
            "Content": "https://dev.file.rehash.redex.eco/58e1b892-ae33-4fad-922e-08dc124b5b70/1704939423946_2024-01-10_170853.png",
            "Name": "2024-01-10_170853.png",
            "Type": {
                "Value": "BankStatement",
                "Description": "Bank statement"
            },
            "CreatedTime": "2024-01-11T02:17:04.61"
        },
        {
            "Id": "52ad534a-0647-49e0-fac2-08dc124b675c",
            "Content": "https://dev.file.rehash.redex.eco/58e1b892-ae33-4fad-922e-08dc124b5b70/1704939424722_2024-01-10_170754.png",
            "Name": "2024-01-10_170754.png",
            "Type": {
                "Value": "LetterOfAuthorization",
                "Description": "Letter Of Authorization"
            },
            "CreatedTime": "2024-01-11T02:17:05.133"
        },
        {
            "Id": "26ad78e6-5a09-4b80-fac3-08dc124b675c",
            "Content": "https://dev.file.rehash.redex.eco/58e1b892-ae33-4fad-922e-08dc124b5b70/1704939442914_2024-01-10_170754.png",
            "Name": "2024-01-10_170754.png",
            "Type": {
                "Value": "CompanyRegistrationDocument",
                "Description": "Company Registration Document"
            },
            "CreatedTime": "2024-01-11T02:17:22.993"
        },
        {
            "Id": "d003cabd-ed14-4b42-fac4-08dc124b675c",
            "Content": "https://dev.file.rehash.redex.eco/58e1b892-ae33-4fad-922e-08dc124b5b70/1704939524943_2024-01-10_165615.png",
            "Name": "2024-01-10_165615.png",
            "Type": {
                "Value": "Kyc",
                "Description": "KYC"
            },
            "CreatedTime": "2024-01-11T02:18:45.007"
        },
        {
            "Id": "f5930c7b-cd76-48dc-fac5-08dc124b675c",
            "Content": "https://dev.file.rehash.redex.eco/58e1b892-ae33-4fad-922e-08dc124b5b70/1704939527042_2024-01-10_170754.png",
            "Name": "2024-01-10_170754.png",
            "Type": {
                "Value": "Aml",
                "Description": "AML"
            },
            "CreatedTime": "2024-01-11T02:18:47.107"
        }
    ],
    "Meta": null,
    "Errors": null,
    "StatusCode": 200,
    "Message": "Success"
}

400 Bad Request

{
  "Data": null
  "StatusCode": 400,
  "Errors": null,
  "Meta": null,
  "Message": "Bad Request"
}

422 Unprocessable Entity

{
  "Data": null
  "StatusCode": 402,
  "Errors": null,
  "Meta": null,
  "Message": "Unprocessable Entity"
}

401 Unauthorized

{
  "Data": null,
  "StatusCode": 401,
  "Errors": null,
  "Meta": null,
  "Message": "Unauthorized"
}

403 Forbidden

{
  "Data": null,
  "StatusCode": 403,
  "Errors": null,
  "Meta": null,
  "Message": "Forbidden"
}

Rate limit

Rate Limit Algorithm: Fixed Window

In fixed window rate limiting, a fixed time window (e.g., one minute, one hour) is used to track the number of requests or actions allowed within that window. Requests exceeding the limit are either rejected or throttled until the window resets.

Rate Limiting Overview

Our API employs rate limiting to ensure fair usage and protect the performance and availability of the service. Combination of Global Policy and Operation Policy

Global Policy

Rate Limit: 3000 requests per 5 minute(s)
Renewal Period: 300 second(s)
Key: IP Address
Increment Condition: Any Request

Operation Policy

Rate Limit: 10 requests per 10 seconds(s)
Renewal Period: 10 second(s)
Key: accound-id business account Id.
Increment Condition: Any Request.

Rate Limit Details

Rate Limit by Key:
1. Key: This ensures that rate limits are applied uniquely for each business account id.
2. Request Limit: Each key is allowed to make up to 10 requests per 10 seconds.
3. Reset Interval: The limit resets every 10 seconds.
Response Headers:
1. Retry-After: Sent when the rate limit is exceeded, indicating how long to wait before making another request.

Exceeding the Rate Limit

When the rate limit is exceeded, the API will return a 429 Too Many Requests status code. The response will include a Retry-After header specifying the number of seconds to wait before making a new request.

Example Response When Rate Limit is Exceeded

HTTP/1.1 429 Too Many Requests
Retry-After: 10
Content-Type: application/json
{
    "Data": null,
    "Errors": null,
    "StatusCode": 429,
    "Message": "Rate limit exceeded",
    "Meta": null
}

[GET] Query Account Profile Documents

Table of Contents