Account API
Retrieve your account details, credit balance, per-minute limits, address quota, and usage history.
The Account API allows you to retrieve detailed information about your Easyparser account, including your current subscription plan, credit balance, per-minute limits, address quota, and usage history.
This endpoint is especially useful for:
Monitoring your remaining credits in real time.
Displaying account details (plan, email, limits) inside dashboards or admin panels.
Creating usage reports on a daily or monthly basis.
Sending notifications when the credit balance is running low.
Integrating billing or quota management workflows.
By using the Account API, you gain better visibility and control over your API consumption and can track limits across Bulk and Real-Time operations.
Endpoint
https://account.easyparser.com/v1/accountRequired Parameter
api_key
String
Query Parameter
Your Easyparser API key used for authentication.
Full Example Request:
Response Fields
request_info.success
Indicates whether the API request was successful.
true
account_info.api_key
The API key associated with the account.
YOUR_API_KEY
account_info.name
The name of the account holder.
MEMBER_NAME
account_info.email
The email address linked to the account.
member_mail@mail.com
account_info.plan
The active subscription plan.
YOUR_PLAN
account_info.credits_used
Total credits used in the current period.
9629
account_info.credits_remaining
Remaining credits available to the account.
990371
account_info.credits_reset_at
When the credits reset (ISO 8601 format).
2028-12-09T08:46:47.000Z
account_info.credits_limit
Maximum credits allowed per billing cycle.
1000000
account_info.minutely_real_time_credit_limit
Maximum Real-Time credits you can spend per minute.
500
account_info.minutely_bulk_credit_limit
Maximum Bulk credits you can spend per minute.
5000
account_info.addresses_used
Number of custom addresses currently in use.
2
account_info.addresses_limit
Maximum number of custom addresses your plan allows.
30
account_info.addresses_available
Number of address slots still available.
2
account_info.usage_history
Historical usage records, with monthly and daily breakdowns.
Array of objects
Usage History (Detailed Structure)
Each entry in usage_history represents one month, ordered newest first.
month
string
usage_history[]
Name of the month (e.g. September).
year
number
usage_history[]
Year of the record.
date
string
usage_history[]
Reference date for the record.
month_number
number
usage_history[]
Zero-based month index (0 = January, so 8 = September).
is_current_month
boolean
usage_history[]
Whether this record is the current month.
account_package_id
number
usage_history[]
Identifier of the plan active during that month.
credits_total_per_day
object
usage_history[]
Per-day usage, keyed by day of month. See below.
month_summary
object
usage_history[]
Totals for the month, as { "success": N }.
Each day inside credits_total_per_day is keyed by the day number and contains:
day_total
object
credits_total_per_day.*
Total successful credits for the day, as { "success": N }.
REALTIME
object
credits_total_per_day.*
Real-Time usage for the day: a total object plus an operations map keyed by operation name.
BULK
object
credits_total_per_day.*
Bulk usage for the day, in the same shape as REALTIME. Present only when bulk requests were made that day.
Within REALTIME and BULK, total holds the day's combined count as { "success": N }, and operations maps each operation name (e.g. DETAIL, SEARCH) to its own { "success": N } count.
Sample Output
Last updated