# Import usage from CSV Upload usage data through the 2Checkout API from a CSV (comma-separated values) file for active and trial subscriptions. Usage data uploaded via JSON-RPC APIv6 will be used to charge subscribers for the metered resources they consume. Metered billing allows for usage fees in arrears to be added to recurring subscription costs. 2Checkout will capture the parameters sent via JSON-RPC APIv6 and import the usage data into the system. Once the upload process is complete, you'll be able to access the uploaded file in the [Usage](https://secure.avangate.com/cpanel/payperusage_management.php) area of the Merchant Control Panel. {% hint style="info" %} Set the DATE parameter to GMT+2 time zone, when making the API call to the Usage Upload endpoint. {% endhint %} ## Method and URL **POST**: ; ## Request parameters

Parameter	Type / Description	Used in HASH validation*
`merchant`	Required (string) Your unique 2Checkout merchant code. View merchant code.	YES
`secret_key`	Required (string) The secret key associated to your account. View secret key.	YES
`file_MD5`	Required (string) The md5 hash of the CSV file used to upload usage.	YES
`hash`	Required (string) The MD5 hmac key for the request.	N/A
`UsageStart`	Required (datetime) The datetime when the usage started; can be the same as `UsageEnd`. For existing records, this will be updated to time 00:00:00.	N/A
`UsageEnd`	Required (datetime) The datetime when the usage ended and was recorded. For existing records this will be updated to time 23:59:59, this will be enforced in the CSV upload as well.	N/A
`OptionCode`	Required (string) Unique codes you provided as identifiers of specific Pricing Options in the Usage Scale Pricing Options Group scheme. Example: metered pricing.	N/A
`Description`	Optional (string) It can be used to store a short merchant comment of the usage being uploaded. This can be anything, from the source of usage (mobile, web, etc.), to why changes occurred, etc. Example: Subscription usage for September.	N/A
`SubscriptionRef`	Required (string) Unique code that represents a subscription. Example: 83FE4FEF2.	N/A

### Request sample ```php ``` ```html ``` ## Error handling | Message code | Message description | Resolution | | ----------------------------------- | ------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------- | | 1 | The upload operation completed successfully. | N/A | | Invalid account! | The merchant code provided does not belong to a vendor in the 2Checkout system. | Please check your merchant code and make sure you're using the correct version. [View merchant code](https://secure.avangate.com/cpanel/account_settings.php). | | Bad signature on the received file! | The upload CSV file's md5 signature is different than the one sent as a parameter. | Please make sure that you're using the correct md5 signature for the CSV file, or that you're uploading the CSV file for which the signature was generated. | | Invalid signature | The HMAC calculated by the 2Checkout system is different from the one you're sending. | Please make sure that all parameters use correct values. | --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.2checkout.com/json-rpc-api-reference/json-rpc-api-6.0/api-requests/usage-management/import-usage-from-csv.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.