Skip to main content
Solved

Can we expose GI Custom Endpoint for outside users?

  • July 22, 2025
  • 6 replies
  • 62 views

Have made one Custom Endpoint under GI which is having User, Roles Entities added and we are able to fetch custom endpoint data using Odata in VMware Postman but want to publish this endpoint for all end-users with valid Acumatica credentials and same endpoint if can be configured in Java Code

POC Description
We are working on a Hyper Scaler project POC and need to build an Acumatica Connector which should extract data from Cdata (serving as the data source) and synchronize it into some Data store. Additionally, it should retrieve detailed Access Control Lists (ACLs) from Cdata and perform ACL synchronization alongside the data sync to ensure least-privilege access for logged in use

Best answer by jinin

@jags 

Clarifying the question in detail,
 I have requirement to use across any organization and any tenants. Will it be possible that we can publish our custom Endpoint globally? -   Yes, you can include the custom endpoint in a customization package and distribute it globally.

However, each organization and tenant must manually install and publish that package in their own Acumatica instance. Acumatica does not support automatic global deployment across different tenants or customer environments.
 

You can build and host your ACL service, but each Acumatica user must connect their own instance to your service.

To do this:

Provide a customization package with the logic and endpoints.

The user installs this in their Acumatica instance.

Your public ACL endpoint is then called from inside Acumatica (via REST calls or automation steps).

So, your endpoint can be public, but each Acumatica instance needs to be configured to use it.

6 replies

jinin
Pro I
Forum|alt.badge.img+11
  • Pro I
  • July 23, 2025

Hi ​@jags,
Create a customization package that includes the Generic Inquiry with your custom endpoint. Publish this package to all tenants so the endpoint is available across the system. In your Java code, use an HTTP client to call the OData URL of the endpoint and fetch the data. This allows you to sync both user-role data and access control lists from Acumatica into your target system.

 


  • Author
  • Freshman I
  • July 24, 2025

Can you help me with any documentation or postman collection which can be used across any public Acumatica instance. 
Also I have requirement to use across any organization and any tenants. Will it be possible that we can publish our custom Endpoint globally?


jinin
Pro I
Forum|alt.badge.img+11
  • Pro I
  • July 24, 2025

Hi ​@jags ,

Can you help me with any documentation or postman collection which can be used across any public Acumatica instance. - I will share the details.

Also I have requirement to use across any organization and any tenants. Will it be possible that we can publish our custom Endpoint globally? -Yes, we can include the custom endpoint in the package and proceed with publishing it globally.

 


jinin
Pro I
Forum|alt.badge.img+11
  • Pro I
  • July 24, 2025

@jags ,
Please find the attached Postman collection and the documentation for creating a custom endpoint using GI

Celigo pakcage | Get Started | Postman API Network.

How to Access Data Efficiently Using Contract-Based APIs

Hope this helps.


  • Author
  • Freshman I
  • July 24, 2025

Thanks much Jinin for quick response!
If we host our custom ACL endpoint for public use, will that be possible for any User to access with their Acumatica Instance?
If yes how?


jinin
Pro I
Forum|alt.badge.img+11
  • Pro I
  • Answer
  • July 24, 2025

@jags 

Clarifying the question in detail,
 I have requirement to use across any organization and any tenants. Will it be possible that we can publish our custom Endpoint globally? -   Yes, you can include the custom endpoint in a customization package and distribute it globally.

However, each organization and tenant must manually install and publish that package in their own Acumatica instance. Acumatica does not support automatic global deployment across different tenants or customer environments.
 

You can build and host your ACL service, but each Acumatica user must connect their own instance to your service.

To do this:

Provide a customization package with the logic and endpoints.

The user installs this in their Acumatica instance.

Your public ACL endpoint is then called from inside Acumatica (via REST calls or automation steps).

So, your endpoint can be public, but each Acumatica instance needs to be configured to use it.