NETONE E-Top Up Webservice Specification

NETONE E-Top Up Webservice
Specification PreRelease version 2.8.2
Contents
1 Summary ......................................................................................................................................... 3
1.1 Methods .................................................................................................................................. 3
2 Set-Up ............................................................................................................................................. 3
2.1 Root endpoint ......................................................................................................................... 3
2.2 Authentication & Auditing ...................................................................................................... 3
2.3 MIME media types .................................................................................................................. 3
2.4 Response codes....................................................................................................................... 3
3 WalletBalance ................................................................................................................................. 4
3.1 Method ................................................................................................................................... 4
3.2 Response ................................................................................................................................. 4
4 End user balance ............................................................................................................................. 4
4.1 Method ................................................................................................................................... 4
4.2 Response ................................................................................................................................. 4
5 Recharge Pinless ............................................................................................................................. 5
5.1 Method ................................................................................................................................... 5
5.2 Method Body .......................................................................................................................... 5
5.3 Response ................................................................................................................................. 5
6 Query A Transaction for reconciliation ........................................................................................... 6
6.1 Method ................................................................................................................................... 6
6.2 Response ................................................................................................................................. 6
7 Data Bundle Recharge ..................................................................................................................... 7
7.1 Method ................................................................................................................................... 7
7.2 Method Body .......................................................................................................................... 7
7.3 Customisation of SMS sent to End User (As Nested JSON object).......................................... 7
7.4 Response ................................................................................................................................. 7
8 Get Available Data Bundles ............................................................................................................. 8
8.1 Method ................................................................................................................................... 8
8.2 Response ................................................................................................................................. 8
8.3 Product Bundle Response Item............................................................................................... 8
Page | 1
9 Query Pin stock ............................................................................................................................... 8
9.1 Method ................................................................................................................................... 8
9.2 Response ................................................................................................................................. 9
10 Bulk EVD PIN purchase ................................................................................................................ 9
10.1 Method ................................................................................................................................... 9
10.2 Method Body .......................................................................................................................... 9
10.3 Return Object .......................................................................................................................... 9
11 Reply Codes and Error Messages .............................................................................................. 10
12 Testing scripts ........................................................................................................................... 15
Page | 2
1 Summary
This is the specification document for the NETONE E-Top Up RESTful Web Service 2.0.
1.1 Methods
There are 4 methods covered in this document that describe the current full functionality of the
Web Service.
1.1.1 Agent Balance
1.1.2 End user balance
1.1.3 Recharge Pinless
1.1.4 Query Transactions
2 Set-Up
2.1 Root endpoint
All Https requests should have the following root:
https://pinlessevd.netone.co.zw/api/v1/
2.2 Authentication & Auditing
To ensure that all requests are properly authenticated it is a requirement that the following custom
headers are passed to the web service.
Field Value
x-access-code The Username the Agent has registered
x-access-password The password the Agent has registered
x-agent-reference A STRING with maximum 50 characters
A unique key to identify the agent’s particular request.
The webservice will not allow duplicate references to be
passed.
2.3 MIME media types
All request bodies and responses will use application/json
2.4 Response codes
The service will return response codes at two levels: 1. HTTP and 2. Application level.
HTTP
HTTP status codes will be used to provide more information about the transport with codes such as
(and not limited to) 200 – Success, 404 – Not found, 400 – Bad Request, 401 – Unauthorized, 500 –
Internal Server Error. Please review the HTTP specification if necessary.
Page | 3
Application
Responses will have ReplyCode and ReplyMessage as fields in their body. These will give more detail
about the exact nature of any issue with respect to the NETONE E-Top Up domain. A more detailed
enumeration of response codes is found in Section 9 Query Pin stock
The method is used for querying PIN stock.
2.5 Method
The Agent Reference in the Header is a specific new Agent reference for this GET Query. The agent
reference passed in the querystring should be one which has previously been used in the custom
headers. See: Authentication & Auditing
Page | 4
GET /agents/query-evd
2.6 Response
Field Value
ReplyCode 2 for Success or for failures is the error code
ReplyMsg Message string with a descriptive result
InStock A Collection of BrandID, BrandName, Denomination and
Quantity
AgentReference The STRING x-agent-reference used to make the request
3 Bulk EVD PIN purchase

The method is for requesting bulk Recharge EVD PIN numbers. It simply supplies the requested
quantity of a single BrandID and values.
3.1 Method
POST /agents/bulk-evd
Field Value
x-access-code As current AccessCode – now part of the header
x-access-password As currently – part of the header
x-agent-reference VarChar(50) (for reconciliation purposes)
3.2 Method Body

The method body to be sent as body parameters, for example ‘{"BrandID": 1, “Denomination”:
0.1, "Quantity”:7000}'
Field Value
BrandID The PIN Brand ID chosen from the list of existing stock of EVD
PINs
Denomination Single Value of an EVD PIN requested in decimal,
Quantity Integer Quantity requested
3.3 Return Object
Field Proposed
ReplyCode 2 for Success or for failures will now be the error code
WalletBalance Agent Account Balance
Amount Total Value of EVD PINs purchased
Discount Decimal value representing the percentage discount.
Page | 5
RechargeID Integer from E-TOP Up
Collection of PINs A collection of PIN objects with fields:
PIN, SerialNumber, BrandID, Denomination, Expiry.
Reply Codes and Error Messages.
4 WalletBalance
4.1 Method
GET /agents/wallet-balance
4.2 Response
Field Value
5 End user balance

5.1 Method
GET /agents/enduser-balance?targetMobile=[mobile number]
5.2 Response
Field Value
MobileBalance Mobile Number Balance of the end user
WindowPeriod If window period information is available (how long is the cell
phone line active on the network)
Page | 6
6 Recharge Pinless
6.1 Method
POST /agents/recharge-pinless
Field Value
x-access-code UserName is part of the header
x-access-password Password is part of the header
6.2 Method Body
The method body to be sent as body parameters, for example ‘{"amount": 0.1, "targetMobile"
: "MobileNumber"}'
Field Value
Amount Decimal currency amount to recharge
TargetMobile National format (077xxxxxxx or 086XXxxxxxx)
BrandID Optional – From a pre-determined list for TXT, DATA and other
Services when available from networks
CustomerSMS Optional – see below
6.2.1 Customisation of SMS sent to End User (As Nested JSON object)
Item Description
CustomerSMS A String with variables as below, which will be
replaced by the service upon successful
recharge and sent to the end-user customer. A
maximum length of 135 Characters is available,
including spaces and returns after replacing the
variables.
Allowed Variables in Format Number of
Custom Response Characters
Message
%AMOUNT% $XXX.XX 7
%INITIALBALANCE% $XXX.XX 7
%FINALBALANCE% $XXX.XX 7
%DATA% XXXX Mb 7
%TXT% XXX Texts 9
%COMPANYNAME% As Defined by Customer on the website www.netone.co.zw
%ACCESSNAME% Defined by Customer on website – Teller or Trusted User or
branch name
6.3 Response
Field Value
Amount Value Recharged
Page | 7
InitialBalance (Optional) Decimal Field representing the Customer’s balance before the
transaction if available
FinalBalance (Optional) Decimal Field representing the Customer’s balance after the
transaction
Window (Optional) DateTime representing the customer’s active period after the
Data (Optional) The amount of Data available after Recharge
SMS (Optional) The number of SMS text messages available after Recharge
RechargeID Integer from NETONE E-Top Up
7 Query A Transaction for reconciliation

The method is for requesting the result of a previous transaction within the last 30 days.
7.1 Method
GET /agents/query-transaction?agentReference=[reference]
Where [reference] is the Agent reference of the original transaction request from the Agent.
7.2 Response
The response will be what should have been returned to the Agent. If the request is still in progress,
pending or busy return codes will be returned and are not final states of the transaction. The Return
Object will differ based on the original transaction type e.g. Recharge Pinless. If the original transaction
cannot be found, an error is returned with the appropriate (new) error code.
7.2.1 For Recharge Pinless
Field Proposed
ReplyCode 2 for Success, 0- Pending (for action) 1- Busy (being processed not
in a final state yet) or for failures will now be the error code 3-
Request not found
ReplyMsg Message about the reply
Success
Pending (for action)
Busy (being processed not in a final state yet)
Request not found
OriginalAgentReference The Agent Reference of the transaction Queried
RawReply As a nested JSON object, the content of the reply to the original
request with the agent reference matching [reference].
Page | 8
8 Data Bundle Recharge
8.1 Method
POST /agents/recharge-data
8.2 Method Body
The method body to be sent as body parameters, for example ‘{"productcode": “ProductCode”,
"targetMobile" : "MobileNumber"}'
Field Value
ProductCode Bundle Product Code
Amount Value of the Bundle (Optional)
TargetMobile As currently national format (077xxxxxxx or 086XXxxxxxx)
CustomerSMS Optional – see below
8.3 Customisation of SMS sent to End User (As Nested JSON object)
Item Description
CustomerSMS A String with variables as below, which will be
replaced by the service upon successful
recharge and sent to the end-user customer. A
maximum length of 135 Characters is available,
including spaces and returns after replacing the
variables.
Allowed Variables in Format Number of
Custom Response Characters
Message
%AMOUNT% $XXX.XX 7
%COMPANYNAME% As Defined by Customer on the website www.hot.co.zw
%ACCESSNAME% Defined by Customer on website – Teller or Trusted User or
branch name
%BUNDLE% Name of the Data Bundle
8.4 Response
Field Value
Amount Bundle Value
InitialBalance (Optional) Decimal Field representing the Customer’s balance before the
FinalBalance (Optional) Decimal Field representing the Customer’s balance after the
transaction
Window (Optional) DateTime representing the customer’s active period after the
Data (Optional) The amount of Data available after Recharge
Page | 9
SMS (Optional) The number of SMS text messages available after Recharge
9 Get Available Data Bundles

9.1 Method
GET /agents/ get-data-bundles
9.2 Response
Field Value
Bundles Bundles is a list of Product Bundle Response Item
9.3 Product Bundle Response Item
Field Value
BundleId Bundle’s Unique Identifier
BrandId (Optional) Brand Category of Bundle
Network Network Provider Name
ProductCode Bundle Product Code to quote when recharging
Amount Data Bundle value in cents
Name Name of Data Bundle
Description Full Description of Data bundle
Validity Period Period of validity for bundle in days
10 Query Pin stock

The method is used for querying PIN stock.
10.1 Method
Page | 10
GET /agents/query-evd
10.2 Response
Field Value
InStock A Collection of BrandID, BrandName, Denomination and
Quantity
11 Bulk EVD PIN purchase

The method is for requesting bulk Recharge EVD PIN numbers. It simply supplies the requested
quantity of a single BrandID and values.
11.1 Method
POST /agents/bulk-evd
Field Value
x-access-code As current AccessCode – now part of the header
x-access-password As currently – part of the header
11.2 Method Body

The method body to be sent as body parameters, for example ‘{"BrandID": 1, “Denomination”:
0.1, "Quantity”:7000}'
Field Value
BrandID The PIN Brand ID chosen from the list of existing stock of EVD
PINs
Denomination Single Value of an EVD PIN requested in decimal,
Quantity Integer Quantity requested
11.3 Return Object
Field Proposed
ReplyCode 2 for Success or for failures will now be the error code
Amount Total Value of EVD PINs purchased
Page | 11
Collection of PINs A collection of PIN objects with fields:
PIN, SerialNumber, BrandID, Denomination, Expiry.
12 Reply Codes and Error Messages
http
Status Reply
code Code ReplyMsg Description and Notes
Your NETONE E-TOP UP Balance is $ #,###.##. You can sell
200 2 approximately $ #,###.##\r\n NetOne E-Top Up Successful Wallet Balance
x-agent-reference header can only be used once. Please Failed Duplicate x-agent-
429 N/A provide a new one for each request. reference
Failed Invalid Login
401 N/A Invalid x-access-code or x-access-password invalid. password or AccessCode
Successful End User Balance.
a negative end user balance
402,The Airtime Balance of 07xxxxxxx is ##.## expiring on can indicate an Netone
200 2 ##/##/2017. contract line
The number 07xxxxxxx you tried to recharge is wrong,
400 217 please check and try again NETONE E-Top Up Failed Web Phone Balance
Recharge to %MOBILE% of $%AMOUNT% was successful.
The initial balance was $%INITIALBALANCE%
200 2 final balance is $%FINALBALANCE% Successful Recharge
Unable to process: %MESSAGE% on the Prepaid platform. Failed Recharge Network
400 210 Please try again later. NETONE E-Top Up Prepaid Platform
Failed invalid end user
The number %MOBILE% you tried to recharge is wrong, network / end user mobile
400 217 please check and try again NETONE E-Top Up number
Your recharge request was too much or too little. Minimum
Recharge %MIN% Maximum Recharge %MAX%, try in the Failed Recharge Amount
400 222 correct range. NETONE E-Top Up Limits
Your recharge for mobile %MOBILE% failed due to
insufficient balance. Your balance is US$ %BALANCE%. You
can sell approximately US$ %SALEVALUE%. NETONE E-Top Failed Insufficient Wallet
400 208 Up. Balance
We are unable to process because the Recharge platform is Failed Recharge VAS
400 206 down. Sorry, NETONE E-Top Up. Your SMS: %MESSAGE% Disabled
We have received your recharge request but do not have
correct stock to process it. Please wait while we send you
400 209 our current stock listing. NETONE E-Top Up Failed Pin Denomination
400 219 Web Service Exception: %MESSAGE% FailedWebException
Login details failed, Please check your accesscode and
401 220 password. Failed Web Login
Page | 12
http
Status Reply
Failed Balance Request.
Possible cause: contract line
200 221 Balance Request not available for %MOBILE% or invalid number
Failed Balance Request.
Possible cause: invalid
number detected before
sending to network, check
400 221 Balance Request not available for %MOBILE% numerical only or format
We have already received this request from you...please
wait while we process it. Thank you, NETONE E-Top Up :
400 216 %MESSAGE% Failed Duplicate
The number %MOBILE% you tried to recharge is wrong, Failed Recharge - Invalid
400 217 please check and try again NETONE Recharge Mobile
You gave an invalid access PIN for transfer of %AMOUNT%
400 218 to %MOBILE%. NETONE E-Top Up Failed Transfer - Access Code
Your recharge request was too much or too little. Minimum
Recharge %MIN% Maximum Recharge %MAX%, try in the Failed Web Recharge
400 222 correct range. NETONE E-Top Up Min/Max
Registration Successful. Your PIN CODE is %PASSWORD%.
Remember your code and delete this message. Further
400 301 instructions will be sent to you shortly. NETONE E-Top Up Successful Registration
Your NETONE E-Top Up Balance is $ %BALANCE%. You can
400 302 sell approximately $ %SALEVALUE%. NETONE E-Top Up Successful Balance
Success %MOBILE% Recharged with $%AMOUNT%
Commission %DISCOUNT%%Cost $%COST% Balance:
$%BALANCE%Sale Value $%SALEVALUE% Thank you for Successful Recharge - Dealer
400 303 choosing NETONE E-Top Up - Header
You purchased $%AMOUNT% Airtime.PINs will be sent to
you shortly.Use these PINs the same as a Scratch card. Successful Recharge Pin -
400 304 Thank you for choosing NETONE E-Top Up. Customer - Header
Pin %PIN%PinReference %REF%Value Successful Recharge Pin -
400 305 $%PINVALUE%Customer %MOBILE%Brand: %BRAND% Dealer
Successful Recharge Pin -
400 306 %PIN% Customer
NETONE topped up your account with $%AMOUNT%.Your Successful Recharge VAS -
400 307 new balance is $%BALANCE%.NETONE E-Top Up Customer
%REF%.Your new balance is $%BALANCE%. You can sell Successful Transfer -
400 308 $%SALEVALUE%. Receiver
Transfer of $%AMOUNT% to %MOBILE% succeeded. Your
new balance $%BALANCE% Thank you for choosing NETONE
400 309 E-Top Up Successful Transfer - Sender
We have reversed your transaction for mobile %MOBILE%
with $%AMOUNT%. Balance: $%BALANCE%. Sale Value
400 310 $%SALEVALUE%. Thank you for choosing NETONE E-Top Up Successful Reversal Dealer
Page | 13
http
Status Reply
The Recharge done in ERROR has been reversed:
$%AMOUNT% debited, your new balance is $%BALANCE%. Successful Reversal
400 311 Thank you for choosing NETONE E-Top Up Customer
NETONE E-Top Up has received your recharge request.
Please wait while it is being processed on the Network
400 312 platform.%MESSAGE% Success Recharge Received
The Airtime Balance of %MOBILE% is %BALANCE% expiring
400 402 on %EXPIRYDATE%. SuccessfulWebPhoneBalance
You purchased $%AMOUNT% Airtime. PINs will be sent to
you shortly.Use these PINs the same as a Scratch card.
Thank you for using %COMPANY% powered by NETONE E- Successful Web Pin -
400 404 Top Up Customer Header
%COMPANY% topped up your Airtime with $%AMOUNT%.
Your new balance is $%BALANCE%. NETONE E-Top Up - 10 Successful Web VAS -
400 407 years the BEST service Customer
Credited %MOBILE%, with %AMOUNT%, Source:
400 500 %SOURCE%, Type: %TYPE%, Ref:% Payment Successful
400 501 Payment Message failed Payment Failed
400 700 %NETWORK% recharge platform webservice timed out. Network Timeout
400 701 %NETWORK% recharge platform connection issue. Network Connection Issue
Network Webservice
400 702 %NETWORK% recharge platform webservice unavailable. Unavailable
400 703 %NETWORK% recharge platform webservice Internal Error Network Webservice Error
Network General Error
400 704 %NETWORK% general platform webservice error.
400 408 Bulk EVD PIN purchase successful for %QUANTITY% of Successful Bulk EVD PIN
Denomination of %DENOMINATION% of request
BrandID: %BRANDID%, Brand: %BRAND%. E-TOP Up
400 409 Bulk EVD PIN purchase successful for %QUANTITY% of Successful Bulk EVD PIN
Denomination of %DENOMINATION% of request
BrandID: %BRANDID%, Brand: %BRAND%. E-TOP Up
400 223 We have received your Bulk EVD request but do not have Failed Pin Denomination
correct stock to process it. E-TOP Up
400 216 We have already received this request from you...please Failed Duplicate
wait while we process it. Thank you, E-TOP Up:
%MESSAGE%
Generic Web responses

1xx Informational
100 Continue
101 Switching Protocols
2xx Successful
Page | 14
http
Status Reply
200 OK
201 Created
202 Accepted
203 Non-Authoritative Information
204 No Content
205 Reset Content
206 Partial Content
3xx Redirection
300 Multiple Choices
301 Moved Permanently
302 Found
303 See Other
304 Not Modified
305 Use Proxy
306 (Unused)
307 Temporary Redirect
4xx Client Error
400 Bad Request
401 Unauthorized
402 Payment Required
403 Forbidden
404 Not Found
405 Method Not Allowed
406 Not Acceptable
407 Proxy Authentication Required
408 Request Timeout
409 Conflict
410 Gone
411 Length Required
412 Precondition Failed
413 Request Entity Too Large
414 Request-URI Too Long
415 Unsupported Media Type
416 Requested Range Not Satisfiable
417 Expectation Failed
5xx Server Error
500 Internal Server Error
501 Not Implemented
502 Bad Gateway
503 Service Unavailable
Page | 15
http
Status Reply
504 Gateway Timeout
505 HTTP Version Not Supported
Page | 16
13 Testing scripts
Here follow several sample testing scripts that should assist in developing the service and viewing
the responses from the web service:
$agentReference = Get-Random
write-host -ForegroundColor Cyan "*** WALLET BALANCE ***"
$headers = @{}
$headers["x-access-code"] = "AccessCode"
$headers["x-access-password"] = "Password"
$headers["x-agent-reference"] = $agentReference
try {Invoke-WebRequest -Uri "https://pinlessevd.netone.co.zw/api/v1/agents/wallet-
balance" -ContentType "application/json" -Headers $headers -Method Get | Format-
List -Property StatusCode,StatusDescription,Content}
catch {Write-Host -ForegroundColor:Red "StatusCode:"
$_.Exception.Response.StatusCode.value__ " StatusDescription:" $_.Exception.message
Write-Host -ForegroundColor:Red $_}
write-host -ForegroundColor Cyan "*** WALLET BALANCE - Duplicate x-agent-reference
***"
$headers = @{}
write-host -ForegroundColor Cyan "*** WALLET BALANCE - Invalid Login password ***"
$headers = @{}
$headers["x-access-password"] = "PasswordFalse"
write-host -ForegroundColor Cyan "*** WALLET BALANCE - Invalid Access-Code ***"
$headers = @{}
$headers["x-access-code"] = "AccessCodeFalse"
$agentReference4 = Get-Random
write-host -ForegroundColor Cyan "*** END USER BALANCE ***"
$headers = @{}
$headers["x-agent-reference"] = $agentReference4
try {Invoke-WebRequest -Uri "https://pinlessevd.netone.co.zw/api/v1/agents/enduser-
balance?targetmobile=MobileNumber" -ContentType "application/json" -Headers
$headers -Method Get | Format-List -Property StatusCode,StatusDescription, Content}
write-host -ForegroundColor Cyan "*** END USER BALANCE - invalid end user Mobile
Number ***"
$headers = @{}
Page | 17
try{Invoke-WebRequest -Uri "https://pinlessevd.netone.co.zw/api/v1/agents/enduser-
balance?targetmobile=MobileNumberX" -ContentType "application/json" -Headers
$headers -Method Get | Format-List -Property StatusCode,StatusDescription, Content}
write-host -ForegroundColor Cyan "*** RECHARGE ***"
$headers = @{}
$body = '{"amount": 0.1, "targetMobile" : "MobileNumber"}'
try{Invoke-WebRequest -Uri "https://pinlessevd.netone.co.zw/api/v1/agents/recharge-
pinless" -Body $body -ContentType "application/json" -Headers $headers -Method Post
| Format-List -Property StatusCode,StatusDescription, Content}
write-host -ForegroundColor Cyan "*** RECHARGE - invalid end user network ***"
$headers = @{}
$body = '{"amount": 0.1, "targetMobile" : "075MobileNumber"}'
write-host -ForegroundColor Cyan "*** RECHARGE - invalid end user Mobile Number
***"
$headers = @{}
$body = '{"amount": 0.1, "targetMobile" : "MobileNumberx"}'
try {Invoke-WebRequest -Uri
"https://pinlessevd.netone.co.zw/api/v1/agents/recharge-pinless" -Body $body -
ContentType "application/json" -Headers $headers -Method Post | Format-List -
Property StatusCode,StatusDescription, Content}
write-host -ForegroundColor Cyan "*** RECHARGE - Min/Max value ***"
$headers = @{}
$body = '{"amount": 0.09, "targetMobile" : "MobileNumber"}'
write-host -ForegroundColor Cyan "*** RECHARGE with Custom Message***"
$headers = @{}
$body = '{"amount": 0.1, "targetMobile" : "MobileNumber", "CustomerSMS": "Custom
SMS from %COMPANYNAME% for a Recharge of
%AMOUNT%
Initial balance $%INITIALBALANCE%
Page | 18
Final Balance $%FINALBALANCE%
The best %COMPANYNAME%
"}'
write-host -ForegroundColor Cyan "*** RECHARGE Agent Dealer insufficient funds***"
$headers = @{}
$body = '{"amount": 50, "targetMobile" : "MobileNumber"}'
write-host -ForegroundColor Cyan "*** QUERY TRANSACTION Agent Reference unknown
***"
$headers = @{}
try{Invoke-WebRequest -Uri "https://pinlessevd.netone.co.zw/api/v1/agents/query-
transaction?AgentReference=$($agentReference2)" -ContentType "application/json" -
Headers $headers -Method Get | Format-List -Property StatusCode,StatusDescription,
Content}
write-host -ForegroundColor Cyan "*** QUERY TRANSACTION Agent Reference can be
found ***"
$headers = @{}
try{Invoke-WebRequest -Uri "https://pinlessevd.netone.co.zw/api/v1/agents/query-
transaction?AgentReference=$($agentReference2)" -ContentType "application/json" -
Headers $headers -Method Get | Format-List -Property StatusCode,StatusDescription,
Content}
write-host -ForegroundColor Cyan "*** Query EVD Stock ***"
$headers = @{}
try{Invoke-WebRequest -Uri "http://pinlessevd.netone.co.zw/api/v1/agents/query-evd"
-UseBasicParsing -ContentType "application/json" -Headers $headers -Method Get |
Format-List -Property StatusCode,StatusDescription, Content}
Page | 19
write-host -ForegroundColor Cyan "*** Bulk Purchase EVD ***"
$headers = @{}
$body = '{"BrandID": 3, “Denomination”: 2, "Quantity”:100}'
try{Invoke-WebRequest -Uri "http://pinlessevd.netone.co.zw/api/v1/agents/bulk-evd"
-Body $body -UseBasicParsing -ContentType "application/json" -Headers $headers -
Method Post | Format-List -Property StatusCode,StatusDescription, Content}
--- End of Document ---
Page | 20

NETONE E-Top Up Webservice Specification

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

NETONE E-Top Up Webservice Specification

Uploaded by

Copyright:

Available Formats

NETONE E-Top Up Webservice

Specification PreRelease version 2.8.2

1.1.1 Agent Balance

1.1.2 End user balance

1.1.3 Recharge Pinless

1.1.4 Query Transactions

All Https requests should have the following root:

2.2 Authentication & Auditing

2.3 MIME media types

All request bodies and responses will use application/json

2.4 Response codes

3 Bulk EVD PIN purchase

3.2 Method Body

3.3 Return Object

Reply Codes and Error Messages.

5 End user balance

GET /agents/enduser-balance?targetMobile=[mobile number]

6.2 Method Body

7 Query A Transaction for reconciliation

7.2.1 For Recharge Pinless

8.2 Method Body

9 Get Available Data Bundles

GET /agents/ get-data-bundles

10 Query Pin stock

11 Bulk EVD PIN purchase

11.2 Method Body

11.3 Return Object

12 Reply Codes and Error Messages

Generic Web responses

--- End of Document ---

You might also like