The HourlyRoleNames API from Bridgit — 1 operation(s) for hourlyrolenames.
Every API here is available over the APIs.io API and to AI agents over MCP.
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
find_apisBrowse and filter every API in the catalog.get_api_artifactsOne API's artifacts, grouped by type.get_openapiThe primary OpenAPI for this API.find_similar_apisAPIs that look like this one.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.curl "https://apis.io/api/v1/apis/bridgit-hourlyrolenames-api"curl "https://apis.io/api/v1/apis?limit=25"Discovery needs no key. Ratings and market analysis are Pro.
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.
openapi: 3.2.0
info:
title: Bench Hourly Role Names API
description: 'Versioning
The API is currently at version 1.0.'
version: '1.0'
servers:
- url: https://bench.gobridgit.com
description: Bridgit Bench production
security:
- {}
tags:
- name: HourlyRoleNames
paths:
/rp/api/v1/accounts/{id}/hourly-role-names:
get:
tags:
- HourlyRoleNames
summary: Get hourly role names in the account
description: 'Permissions
Account: Read
Finance: Read
HourlyRole: Read'
operationId: HourlyRoleNames_Get
parameters:
- name: id
in: path
description: The account ID
required: true
schema:
type: integer
format: int32
responses:
'200':
description: Success
content:
text/plain:
schema:
type: array
items:
$ref: '#/components/schemas/HourlyRoleNameResponse'
application/json:
schema:
type: array
items:
$ref: '#/components/schemas/HourlyRoleNameResponse'
text/json:
schema:
type: array
items:
$ref: '#/components/schemas/HourlyRoleNameResponse'
'400':
description: Bad Request
'401':
description: Unauthorized
'403':
description: Forbidden - User doesn't have permissions on this resource, or the project couldn't be found
post:
tags:
- HourlyRoleNames
summary: Add/Update hourly role name(s) in the account
description: 'If "alphabetize" parameter flag is true, the role names should be alphabetically ordered by caller, otherwise in the order of the request.
To add or update role names you must have permissions to manage account properties.
Permissions
Account: Write
HourlyRole: Write'
operationId: HourlyRoleNames_Post
parameters:
- name: id
in: path
description: The account ID
required: true
schema:
type: integer
format: int32
- name: alphabetize
in: query
description: Optional flag to set whether role names should be alphabetically ordered by the caller
schema:
type: boolean
default: false
requestBody:
description: The role name detail
content:
application/json-patch+json:
schema:
minItems: 1
type: array
items:
$ref: '#/components/schemas/HourlyRoleNameRequest'
application/json:
schema:
minItems: 1
type: array
items:
$ref: '#/components/schemas/HourlyRoleNameRequest'
text/json:
schema:
minItems: 1
type: array
items:
$ref: '#/components/schemas/HourlyRoleNameRequest'
application/*+json:
schema:
minItems: 1
type: array
items:
$ref: '#/components/schemas/HourlyRoleNameRequest'
required: true
responses:
'200':
description: Success
content:
text/plain:
schema:
type: array
items:
$ref: '#/components/schemas/HourlyRoleNameResponse'
application/json:
schema:
type: array
items:
$ref: '#/components/schemas/HourlyRoleNameResponse'
text/json:
schema:
type: array
items:
$ref: '#/components/schemas/HourlyRoleNameResponse'
'400':
description: Bad Request - Request has missing or invalid values
'401':
description: Unauthorized
'403':
description: Forbidden - User doesn't have permissions on this resource, or the project couldn't be found
delete:
tags:
- HourlyRoleNames
summary: Remove hourly role name(s) by ID in the account
description: 'To remove hourly role names you must have permissions to manage account properties.
NOTE: The account must contain at least 1 role name.
Permissions
Account: Write
HourlyRole: Write'
operationId: HourlyRoleNames_Delete
parameters:
- name: id
in: path
description: The account ID
required: true
schema:
type: integer
format: int32
requestBody:
description: The IDs of the role name to be removed
content:
application/json-patch+json:
schema:
minItems: 1
type: array
items:
type: integer
format: int64
application/json:
schema:
minItems: 1
type: array
items:
type: integer
format: int64
text/json:
schema:
minItems: 1
type: array
items:
type: integer
format: int64
application/*+json:
schema:
minItems: 1
type: array
items:
type: integer
format: int64
required: true
responses:
'204':
description: No Content - Success
'401':
description: Unauthorized
'403':
description: Forbidden - User doesn't have permissions on this resource, or the project couldn't be found
'422':
description: Validation failed - if the role name is being used by any role, the name cannot be removed
components:
schemas:
HourlyRoleNameRequest:
type: object
properties:
id:
type: integer
format: int64
example: 1
name:
type:
- string
- 'null'
example: Project Engineer
hourlyCost:
type:
- number
- 'null'
format: double
example: 123.45
additionalProperties: false
HourlyRoleNameResponse:
type: object
properties:
id:
type: integer
format: int64
example: 1
name:
type:
- string
- 'null'
example: Project Engineer
type:
enum:
- Salaried
- Hourly
- All
type: string
example: Salaried
hourlyCost:
type:
- number
- 'null'
format: double
example: 123.45
inUse:
type: boolean
readOnly: true
projectIds:
type:
- array
- 'null'
items:
type: integer
format: int64
example:
- 1
alphabetize:
type: boolean
additionalProperties: false
securitySchemes:
Bearer:
type: http
description: Standard Authorization header using the Bearer scheme
scheme: bearer
bearerFormat: JWT