# Script-2-API (Groovy / JS) — Use case > Drop a Groovy or JavaScript snippet — it ships as a governed REST endpoint. Auth, audit, rate limits, and OpenAPI come included. No container builds, no service code. *Developers · Scripts → API · For developers* ## Write the logic. Ship the API. Skip the service. Script-2-API turns a Groovy or JavaScript snippet into a governed REST endpoint. The runtime sandboxes execution, applies platform controls, and gives you an OpenAPI spec for free. [Five-minute quickstart](https://apinizer.com/developers/quickstart) · [Open Script to API](https://apinizer.com/products/script-to-api) --- ## The problem *The problem* ### Not every endpoint deserves a microservice. A transform here, a calculation there, a small enrichment over a third-party API — none of these need a Docker image, a Helm chart, or a six-week onboarding to the platform. Apinizer's Script-2-API lets engineers drop a Groovy or JavaScript snippet into a governed runtime: same auth, same audit, same rate limits, none of the boilerplate. --- ## Capabilities ### Groovy or JavaScript Pick the language that fits the team. Both run inside a sandboxed runtime with the same lifecycle hooks. ### Governed by default Every Script-2-API endpoint inherits auth, rate limits, audit, and encryption — the same controls every other endpoint has. ### OpenAPI generated Declare parameters and response shape; OpenAPI ships automatically. Partners discover scripts the way they discover REST APIs. ### Sandboxed runtime Scripts run inside guardrails — no arbitrary filesystem, no unscoped network. Resources controlled by the platform. ### Outbound to anything Scripts can call upstream APIs, databases (via connectors), or message queues — through the same governed channels the gateway uses. ### Audit captures the script Every change to the script writes to audit. Auditor sees the version that ran, who deployed it, and the request that triggered it. --- ## Real-world examples ### Banking **Scenario:** Istanbul bank ships 60 enrichment scripts in three weeks **Outcome:** Each script enriches a core-banking call with risk-score or KYC data. No new services; no container images; same audit posture as the legacy stack. **Metric:** 60 endpoints, 0 containers ### Insurance **Scenario:** Frankfurt insurer wraps actuarial scripts as APIs **Outcome:** Groovy actuarial calculators that used to live in a spreadsheet are now governed endpoints. Auditor signs off because audit covers every call. ### Public sector **Scenario:** Stockholm agency exposes simple lookups as JS endpoints **Outcome:** Junior engineers ship a new endpoint in one afternoon; the platform team only reviews policy, not boilerplate. ### Retail **Scenario:** Madrid retailer transforms partner payloads with JS scripts **Outcome:** Each partner has slightly different field names. Script maps them; the downstream service sees a clean shape. ### Telecom **Scenario:** Amsterdam carrier composes 3 backend calls into one customer view **Outcome:** Groovy script fans out to billing, network, and CRM; assembles the response. No new microservice; same auth and audit. ### Media **Scenario:** Milan publisher A/B-tests a recommendation logic with scripts **Outcome:** Two scripts behind one endpoint; routing splits 50/50. New logic wins; promotion is one policy change. ### Energy **Scenario:** Prague utility transforms SCADA payloads on the gateway **Outcome:** Tag mappings, unit conversions, and enrichment ship as scripts. SCADA team keeps its protocol; consumers get a clean API. ### Government **Scenario:** Baku ministry handles partner-specific quirks via scripts **Outcome:** Each partner integration has its own normalization script. New partner onboarded in two days; previous version preserved in audit. --- ## Recommended modules - [Script to API](https://apinizer.com/products/script-to-api) — Drop Groovy or JavaScript into a governed runtime — it ships as a REST endpoint. - [API Creator](https://apinizer.com/products/api-creator) — Script-2-API alongside DB-2-API and Mock API. - [API Gateway](https://apinizer.com/products/api-gateway) — Runtime that applies the platform's auth, rate limit, and audit to every script. - [API Integrator](https://apinizer.com/products/api-integrator) — Scripts can call into the same connector library as task flows. --- ## Resources - [Script-2-API overview](https://docs.apinizer.com/en) — Sandboxing, lifecycle, governance, and OpenAPI generation. - [Script to API product](https://apinizer.com/products/script-to-api) — Groovy / JavaScript snippets as governed endpoints. - [API Creator hub](https://apinizer.com/products/api-creator) — DB-2-API, Mock API, Script-2-API together. - [APIops manifests](https://apinizer.com/developers/apiops) — Ship scripts as code, review in Git, apply idempotently. - [Analytics Engine](https://apinizer.com/products/analytics-engine) — Per-endpoint telemetry — including every Script-2-API. - [Architecture overview](https://docs.apinizer.com/en/concepts/architecture) — Where Script-2-API runs in the platform topology. --- ## Related use cases - [DB-2-API](https://apinizer.com/solutions/db-2-api) — For developers - [Mock APIs](https://apinizer.com/solutions/mock-apis) — For developers - [Connector library (15+)](https://apinizer.com/solutions/connector-library) — For developers - [OpenAPI-first design](https://apinizer.com/solutions/openapi-first) — For developers --- ## Next step *Code into endpoints* **Write the logic. Skip the service.** A 30-minute walkthrough — drop a script, declare params, ship — on a Kubernetes of your choice. [Book a Demo](https://calendly.com/apinizer/15min) · [Read the docs](https://apinizer.com/developers/docs) --- ## Links - Products: https://apinizer.com/products - AI Gateway: https://apinizer.com/products/ai-gateway - Solutions: https://apinizer.com/solutions - Pricing: https://apinizer.com/pricing - Developers: https://apinizer.com/developers - Documentation: https://docs.apinizer.com/index-en - Blog: https://apinizer.com/blog - Contact: https://apinizer.com/company/contact © 2026 Apinizer. All rights reserved.