CPO Sessions
No OAuth-enabled endpoints in this section. Turn off the OAuth filter in the sidebar to see all of its endpoints.
CPO Session Endpoints
Get Payment Terminal Session
Sessions that are run via Payment Terminals result in an additional entity that we dub a Payment Terminal Session. Payment Terminal Sessions are used to coordinate sessions authorized via Payment Terminals, in addition to storing any relevant payment information.
Note that not all Payment Terminal sessions result in funds drawn from external sources; some Payment Terminals also support taps from typical EV charging RFID tags/cards. The cardType field can be used check what flavour of card was used.
The id value can be obtained from the evsePaymentTerminalSessionId field of a CPO session.
User sessionAPI credentialcpo-sessions:readPath parameters1
200OK application/json
dataEvsePaymentTerminalSessionResource
metaobject
400Invalid Request application/json
errorobject
401Unauthorized application/json
errorobject
403Forbidden: missing a required permission, or no access to this resource application/json
errorobject
404Not Found application/json
errorobject
500Internal server error application/json
errorobject
Search CPO Sessions
This endpoint allows for searching of CPO sessions using various filters. It is optimized for speed and supports pagination. The response includes a list of sessions and metadata about the pagination.
User sessionAPI credentialcpo-sessions:readRequest bodyapplication/json
createdAtobject
to-eurendedAtobject
externalCalculatedPriceobject
sessions-cpo.csvjsonkwhobject
50reimbursementAmountobject
otherplatformtotaldeliveredfailedpendingsyncedunsynced0sortobjectdefault {"field":"endedAt","order":"desc"}
{"field":"endedAt","order":"desc"}ascdescACTIVECOMPLETEDtotalCostobject
updatedAtobject
200OK application/json
dataobject[]
authorizationobject
paymentobject
sourceobject
evseControllerobject
exchangeRateobject
locationobject
priceWithFXobject
cporawRecordobject
reimbursementobject
Tri-state: absent or null means the external funder has not answered yet.
syncobject
ocpiobject
validityobject
vatInfoobject
metaobject
400Invalid Request application/json
errorobject
401Unauthorized application/json
errorobject
403Forbidden: missing a required permission, or no access to this resource application/json
errorobject
404Not Found application/json
errorobject
500Internal server error application/json
errorobject
Get Session
User sessionAPI credentialcpo-sessions:readPath parameters1
200OK application/json
dataCpoSessionResource
billingPlanobject
metaobject
400Invalid Request application/json
errorobject
401Unauthorized application/json
errorobject
403Forbidden: missing a required permission, or no access to this resource application/json
errorobject
404Not Found application/json
errorobject
500Internal server error application/json
errorobject
Get Session Reimbursements
Returns dedicated reimbursement records for a CPO session. These records are reliable only when the session explicitly has dedicated reimbursement records enabled.
User sessionAPI credentialcpo-sessions:readPath parameters1
Query parameters1
200OK application/json
dataSessionReimbursementResource[]
businessReimbursecommunityReimburseemployeeReimbursenoReimbursesplitReimburseaccountobjectOnly populated when the request passes include=accountId, and then only with the account's name.
Only populated when the request passes include=accountId, and then only with the account's name.
How the amount was calculated. Not authoritative.
The session's endedAt, which is the billing date of the reimbursement.
reimbursementAmountobjectREQUIREDThe amount being reimbursed. Authoritative.
The amount being reimbursed. Authoritative.
vatRuleVatRuleREQUIRED
exactnetsuiteERP-facing counterpart of exactVatCode. Mixed in Mongo: existing documents hold both strings and numbers.