Rippling: DELETE Job Code
Rippling tandAapi.delete: arguments, response, policy and SDK examples.
← Tand aapi operations · Get started
Operation rippling.t_and_a_api.delete
Provider route: DELETE /platform/api/job_codes/{job_code_id}. Alter supplies the connection’s credentials and routing.
Call through Alter
Section titled “Call through Alter”Install @alter-ai/sdk @alter-ai/rippling with npm, or alter-sdk-rippling with pip. Supply your connected customer’s grant ID and the arguments described below.
import { App } from "@alter-ai/sdk";import { RipplingIntegration } from "@alter-ai/rippling";
async function execute(input: Parameters<RipplingIntegration["tandAapi"]["delete"]>[0]) { const app = new App({ apiKey: process.env.ALTER_API_KEY! }); try { const provider = new RipplingIntegration(app, { grantId: process.env.PROVIDER_GRANT_ID! }); const call = await provider.tandAapi.delete(input); const result = await call.wait(); return result.bodyJson(); } finally { await app.close(); }}import osfrom alter_sdk import Appfrom alter_sdk_rippling import RipplingIntegration
async def execute(arguments): async with App(api_key=os.environ["ALTER_API_KEY"]) as app: provider = RipplingIntegration(app, {"grant_id": os.environ["PROVIDER_GRANT_ID"]}) call = await provider.tand_aapi.delete(arguments) result = await call.wait() return result.body_json()| Field | Type | Presence | Description and constraints |
|---|---|---|---|
$ | object | Root | Additional keys: not allowed |
path | object | Required within parent | Additional keys: not allowed |
path.job_code_id | string | Required within parent |
Response
Section titled “Response”Response media type: application/json. The table describes the pinned successful response. Referenced models link to their complete fields.
| Field | Type | Presence | Description and constraints |
|---|---|---|---|
$ | Model | Root | Expand GET Job Code — response body |
Referenced models: GET Job Code — response body
Schemas
Section titled “Schemas”GET Job Code — response body
| Field | Type | Presence | Description and constraints |
|---|---|---|---|
$ | object | Root | A job code object is a specific instance of an option underneath a dimension that time can be tracked against. If the configured dimension were to be 'Location', for example, job code options underneath that dimension might include 'San Francisco', 'New York', 'Bangalore', etc. |
dimension | string | Required within parent | The id of the associated dimension. |
group | string or null | Optional | The id of the group that applies to the job code, if one exists. |
id | string | Required within parent | The id of the job code. |
spoke_identifier | string or null | Optional | The unique identifier of the job code in an outside system. |
value | string | Required within parent | The name of the job code. |
Policy, approvals and errors
Section titled “Policy, approvals and errors”SDK function policy ID: rippling.t_and_a_api.delete. Catalog operation: t-and-a-api.delete. Rules can name either ID; function rules distinguish managed calls and conservatively cover raw calls sharing the route. Existing grant permissions and policy rules apply. wait() returns an immediate result or waits for a required approval; it never approves the request itself. Persist the approval ID to resume after a restart.
Provider errors retain their response; JSON decoding raises ProviderAPIError for provider failures. ManagedOperationError identifies contract/input/retention errors. See error handling and provider-specific behavior. Sensitive input may be refused before approval storage. A decoding error never resubmits a write.