





























































































.webp)












Ellucian Banner is a comprehensive ERP platform for higher education, managing student information, financial aid, admissions, and administrative processes across campuses.
Have any questions? We’re here to help You
All API requests require authentication via bearer token. After successfully connecting a system through Makini's authentication module, you receive an API token. Include this token in the Authorization header of your requests: Authorization: Bearer YOUR_API_TOKEN. Each connection has a unique token, allowing you to manage multiple customer connections independently. Tokens remain valid as long as the underlying system credentials are valid and the connection is active. If a customer changes their system credentials, you'll need to reconnect to obtain a new token.
You need two essential prerequisites:
Administrator access to your NetSuite account
API Integration enabled in your NetSuite account
Makini's unified API acts as a common denominator across all connected systems. We map each system's data structure to a standardized data model, exposing consistent endpoints regardless of the underlying platform. This means you write the same code to retrieve purchase orders from SAP, NetSuite, or Dynamics—the API calls and response formats are identical. You always get data in the same structure, making it easy to build consistent business logic. The unified approach eliminates the need to learn each system's unique API, manage multiple authentication methods, or handle varying data formats.
Makini's API supports date filtering on most endpoints using query parameters. You can filter by creation date, modification date, or entity-specific date fields like order date or delivery date. Common patterns include modified_after=2024-01-01 to retrieve records updated since a specific date, or relative timestamps like modified_after=2024-01-01T00:00:00Z. For optimal performance, use incremental data retrieval patterns rather than repeatedly fetching all records. The sync status endpoint provides the last sync timestamp, which you can use as the modified_after value for your next query. This approach minimizes data transfer and API load while ensuring you capture all changes.
