Introduction
Welcome to the CekResi API documentation. Our API provides access to shipping tracking services and Indonesian region data through the BinderByte API.
Base URL
https://api.cekresi.biz.id
Current Version
v1
All API requests should be made over HTTPS. Calls made over plain HTTP will fail.
System Architecture
Our system uses a managed API key approach where API keys are stored in a database and automatically rotated based on usage limits. Users do not need to provide their own API keys.
How It Works
- API keys are securely stored in MongoDB database
- System automatically selects an available API key for each request
- Usage is tracked and monitored to prevent quota exhaustion
- Multiple API keys can be configured for redundancy
- No authentication required from end users
While there is no direct rate limiting for end users, the system manages API key quotas internally to ensure service availability.
Cek Resi Endpoint
GET
https://api.cekresi.biz.id/api/v1/resi/{kurir}/{nomor_resi}
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
| kurir | string | Required | Kode kurir (jne, pos, jnt, etc.) |
| nomor_resi | string | Required | Nomor resi paket |
Response Example
{
"status": 200,
"message": "Success",
"data": {
"summary": {
"courier": "JNE",
"awb": "JP1234567890",
"status": "DELIVERED",
"date": "2023-10-15 14:30:00",
"desc": "Paket telah diterima oleh penerima",
"amount": "12000"
},
"detail": {
"shipper": "PT. Toko Online",
"receiver": "John Doe"
},
"history": [
{
"date": "2023-10-15 14:30:00",
"desc": "Paket telah diterima oleh penerima",
"location": "Jakarta Selatan"
},
{
"date": "2023-10-15 09:15:00",
"desc": "Paket sedang dalam proses pengiriman",
"location": "Jakarta Selatan"
}
]
}
}
List Kurir Endpoint
GET
https://api.cekresi.biz.id/api/v1/kurir
Parameters
None
Response Example
{
"status": 200,
"message": "Success",
"data": [
{
"code": "jne",
"description": "Jalur Nugraha Ekakurir (JNE)"
},
{
"code": "pos",
"description": "POS Indonesia"
},
{
"code": "jnt",
"description": "J&T Express"
}
]
}
Wilayah Endpoints
GET
https://api.cekresi.biz.id/api/v1/wilayah/provinsi
Get List Provinsi
Response Example
{
"status": 200,
"message": "Success",
"data": [
{
"id": "11",
"name": "ACEH"
},
{
"id": "12",
"name": "SUMATERA UTARA"
}
]
}
GET
https://api.cekresi.biz.id/api/v1/wilayah/kabupaten/{id_provinsi}
Get List Kabupaten/Kota
| Name | Type | Required | Description |
|---|---|---|---|
| id_provinsi | string | Required | ID provinsi |
GET
https://api.cekresi.biz.id/api/v1/wilayah/kecamatan/{id_kabupaten}
Get List Kecamatan
| Name | Type | Required | Description |
|---|---|---|---|
| id_kabupaten | string | Required | ID kabupaten/kota |
GET
https://api.cekresi.biz.id/api/v1/wilayah/kelurahan/{id_kecamatan}
Get List Kelurahan/Desa
| Name | Type | Required | Description |
|---|---|---|---|
| id_kecamatan | string | Required | ID kecamatan |
Error Handling
The CekResi API uses conventional HTTP response codes to indicate the success or failure of an API request.
| Code | Description |
|---|---|
| 200 | OK - Request successful |
| 400 | Bad Request - Invalid request parameters |
| 404 | Not Found - Resource not found |
| 500 | Internal Server Error - Something went wrong on our end |
Error Response Format
{
"status": 400,
"message": "Invalid courier code",
"data": null
}
Usage Guidelines
Our service is designed for fair usage by all users:
Fair Usage Policy
- No API key required for end users
- No explicit rate limiting imposed on individual users
- System automatically manages API key quotas behind the scenes
- Please use the service responsibly and avoid excessive requests
- For high-volume usage, please contact us for dedicated access
Best Practices
- Cache results when possible to reduce unnecessary requests
- Handle errors gracefully in your applications
- Validate input parameters before making requests
- Monitor your application for any unusual behavior
If you experience any issues or have questions about usage limits, please contact our support team.