Asanify

The Asanify Partner API is a private, read-only HTTP API your ERP or data warehouse uses to pull HR and payroll data out of Asanify. Start here for what it…

Partner API: what it is, and what it is not

How to send your API key, what the base URL is, and how to prove the whole thing works with one curl command before you write any code.

Partner API: authentication and your first call

Your key can only call the endpoints its scopes cover. This lists every scope, the exact endpoints each one opens, which are treated as heightened-sensitivity, and how to request one.

Partner API: scopes, and how to ask for more

The rules that hold across every endpoint: how paging works, how to narrow a response with ?fields=, and the difference between asan_empcode and employee_id.

Partner API: pagination, field selection and identifiers

Every error shares one JSON envelope. This is what is in it, what each HTTP status means, and why your code should branch on message_key rather than on the English…

Partner API: errors and the message_key contract

Two per-key rate limits apply, and a 429 does not carry the usual JSON error envelope. This is what the limits are and how to build a retry that works.

Partner API: rate limits and the 429 response

The employee directory is where almost every integration starts: it is the list your ERP reconciles against, and the source of the employee code the payroll and salary endpoints join…

Partner API: the employee directory

Your legal entities are the companies payroll is actually run under. Their ids are what the entity_id filter on the other endpoints accepts.

Partner API: legal entities

Payroll comes in two layers: the run summaries, which are totals per run, and one run's per-employee lines. They need different scopes, because the second is per-person pay.

Partner API: payroll runs

Salary structures are what an employee is contracted to be paid, itemised by component. This is different from payroll, which is what was actually paid in a given run.

Partner API: salary structures

Contractors are a different population from employees and are not in the payroll endpoints. Their payments are keyed on the date they were processed, not on a pay month.

Partner API: contractor payments

Leave balances are per employee and per policy, as of a date you choose.

Partner API: leave balances

Departments, designations, work locations and the salary-component catalogue are the master data the other endpoints refer to by name or by id. They all sit behind one scope and change…

Partner API: reference data

Bank details are the destination for a real money transfer, and this endpoint returns account numbers unmasked. It is the most restricted thing in this API and is not part…

Partner API: bank details

Use a partner API key to let your ERP or HRIS pull data like people, payroll runs and leave balances directly from Asanify. This article covers finding the page, creating…

As an Admin, how do I manage my partner API keys in Asanify?

Vaibhav Kashyap

Partner API

Existing user? Login

New user? Sign up now

Demo

Videos

No tickets or conversations found

Try selecting a different creation date range.

Tickets and conversations you've started through the messenger will appear here.

No tickets or conversations created by you

Try using different keywords or checking for typos.

Try selecting a different update date range.

Find answers and get help from Intercom Support and Community Experts

Conversations you've started through the messenger will appear here.

No conversations created by you

No conversations found

AI title

Title

This site employs cookies and other technologies that we and our third party vendors use to monitor and record personal information about you and your interactions with the site (including content viewed, cursor movements, screen recordings, and chat contents) for the purposes described in our Cookie Policy. By continuing to visit our site, you agree to our {websiteTermsLink}, {privacyPolicyLink} and {cookiePolicyLink}.

This site uses cookies and similar technologies ("cookies") as strictly necessary for site operation. We and our partners also would like to set additional cookies to enable site performance analytics, functionality, advertising and social media features. See our {cookiePolicyLink} for details. You can change your cookie preferences in our Cookie Settings.

We use cookies to make our site work and also for analytics and advertising purposes. You can enable or disable optional cookies as desired. See our {cookiePolicyLink} for more details.

Advertising cookies are set by our advertising partners to collect information about your use of the site, our communications, and other online services over time and with different browsers and devices. They use this information to show you ads online that they think will interest you and measure the ads' performance. Social media cookies are set by social media platforms to enable you to share content on those platforms, and are capable of tracking information about your activity across other online services for use as described in their privacy policies.

These cookies enable the website to provide enhanced functionality and personalisation. They may be set by us or by third party providers whose services we have added to our pages. If you do not allow these cookies then some or all of these services may not function properly.

These cookies are necessary for the website to function and cannot be switched off in our systems.

These cookies allow us to count visits and traffic sources so we can measure and improve the performance of our site. They help us to know which pages are the most and least popular and see how visitors move around the site.

You have the right to opt out of the sale of your personal information. See our {cookiePolicyLink} for more details about how we use your data.

Your Privacy Choices

We use cookies to enhance your experience. You can customize your cookie preferences below. See our {cookiePolicyLink} for more details.

Cookie Settings

Empty Help Center

Uh oh. That page doesn’t exist.

Home

Search results

Disappointed

Neutral

Smiley

Thinking...

Searching through sources...

Analyzing...

Tickets submitted through the messenger or by a support agent in your conversation will appear here.

No tickets created by you

No tickets found

Conversations and tickets in {topic}

Conversations and tickets in {topic} // {subtopic}

Volume, creators and topics for your company.

Insights

Top creators

AI topics

Track the progress of all tickets and conversations related to your company.

Customer Portal.

Track the progress of all tickets related to your company.

Tickets portal.

{assigneeName} needs more information from you

Tickets

No access to tickets portal

Search

Skip the search. Describe what you’re trying to do and get a grounded answer.

Browse articles and guides in this topic.

Create your workspace and invite the people you work with.

Set up your account

Build your first workflow and watch it run end to end.

Ship something

Connect the tools your team already uses to bring data in.

Connect your stack

A quick lap of the product so you know where everything lives.

{appName} in 60 seconds

This prototype demo is aware that you are reading “{title}”. It can point you back to the current article, but a production article-aware Fin contract is still follow-up work.

Prototype article-aware answer

Because you already asked about invitations, this prototype demo can add the follow-up: use the role selector before sending each invite to limit access to the teammate responsibilities.

Prototype role-limiting follow-up

This prototype demo suggests starting with your workspace profile, inviting the team members who need access, and then connecting the integrations you use.

Prototype getting-started answer

In this prototype demo, integrations are configured from workspace settings. Choose the integration, connect the account, and review the enabled permissions.

Prototype integrations answer

In this prototype demo, invite teammates from workspace settings, then choose the access each teammate needs before sending the invitation.

Prototype invite-team answer

This prototype demo does not have a scripted answer for that question yet. Try asking how to invite your team or open a source article. No production Fin API was called.

Prototype answer unavailable

I’ve got this page open. Ask me anything about it and I’ll answer from the docs.