REST API Integration queries

[Pranita2]

Hello folks,

We are implementing two REST API Integrations into the instance. I had a query that what would be the charges which Service Now has on REST Integrations.

All that which the customer should be aware of

Any quick help is much appreciated.

Thanks,

Pranita Bahuguni

[Richard Hine]

Pranita2,

If you use platform System Web Services->Outbound->REST Message and System Web Services->Scripted Web Services->Scripted REST APIs then there should be no charge as they are part of the platform.

If you use REST Messaging via Flow Designer/Integration Hub, you will need an Integration Hub subscription and each use will be counted in your activation count.

Hope this helps,

Richard

[ersureshbe]

Hi, If the customer is not ready to invest to subscribe to the IntegrationHub you can use import set table, ECC retry plugin(free of cost) , script include and business rule etc.,

[BellBoy]

ServiceNow typically does not charge directly for using REST API integrations within your instance, as the functionality is included with your subscription. However, there are key considerations and potential costs associated with implementing and maintaining REST API integrations:

1. Subscription Costs
Base Subscription: ServiceNow charges for the platform's subscription, which typically includes access to REST API capabilities as part of your instance.
Additional Plugins: Some advanced features or integrations may require enabling paid plugins, such as IntegrationHub, which might incur additional costs.
2. Licensing Impacts
IntegrationHub Usage: If you use ServiceNow's IntegrationHub for building REST-based flows, your license might include a specific number of transactions (e.g., actions or requests). Exceeding the transaction limits could lead to overage fees.
External Application Licensing: If the REST integration involves external third-party APIs, you may face licensing or usage fees imposed by the API provider.
3. Infrastructure Costs
API Traffic Volume: High-volume API traffic might increase resource usage on your ServiceNow instance, potentially impacting performance or necessitating higher-tier ServiceNow plans.
ServiceNow Instance Size: If the integration significantly increases data volume (e.g., importing large datasets), storage limits might be exceeded, and additional storage costs could apply.
4. Implementation and Maintenance Costs
Development Efforts: Developing, testing, and maintaining custom REST API integrations often requires developer time and expertise.
Ongoing Maintenance: REST API integrations require regular maintenance to ensure compatibility with updates to ServiceNow and the external APIs.
Third-Party Middleware: If you use middleware for managing integrations, there could be licensing and maintenance costs.
5. Security and Compliance Considerations
Encryption and Certificates: Managing secure connections might require purchasing SSL/TLS certificates or other security tools.
Audit and Compliance: Depending on your organization's compliance requirements, you may need additional audits or monitoring, which could add costs.
6. Customer Awareness
To ensure your customer is fully informed:

Subscription Details: Confirm the licensing terms and transaction limits in their ServiceNow agreement.
IntegrationHub Licensing: Clarify if IntegrationHub actions are included or if they are limited.
Third-Party API Costs: Notify customers about any charges associated with using external APIs.
Support and Maintenance: Set expectations for the ongoing support and potential costs of maintaining the integration.
Scalability Considerations: Discuss how increasing usage might impact licensing or infrastructure costs.