How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Fieldguide

Fieldguide requests API

Endpoints used to interact with Fieldguide Requests

Documentation Provider Profile APIs.io OpenAPI GitHub

Fieldguide requests API is one of 15 APIs that Fieldguide publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Requests. The published artifact set on APIs.io includes an OpenAPI specification, an API reference, and API documentation.

This API exposes 11 operations across 8 paths, and defines 17 schemas. It is described by OpenAPI 3.0.0, at version v1.

Requests are made against a single base URL, https://api.fieldguide.io.

11 operations 8 paths 17 schemas 7 GET1 PATCH3 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.0
API Version
v1
Base URL
https://api.fieldguide.io
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Fieldguide requests API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (bearer). By default, every request must be authenticated.

Paths & Operations 11

Across 8 paths, the API surfaces 11 operations — 7 GET, 1 PATCH, 3 POST. Each is listed below with its method, path, parameters, and response codes.

requests 11

Endpoints used to interact with Fieldguide Requests

GET
/v1/requests/{uuid}/controls
List Controls that belong to the specified Request
list_controls_by_request_v1 4 params → 200400401403404429
GET
/v1/engagements/{uuid}/requests
List Requests that belong to the specified Engagement
list_requests_by_engagement_v1 7 params → 200400401403404429
GET
/v1/sheet-rows/{uuid}/requests
List Requests that belong to the specified Sheet Row
list_requests_by_sheet_row_v1 4 params → 200400401403404429
GET
/v1/requests/{uuid}
Fetch the specified Request
get_request_v1 1 param → 200400401403404429
PATCH
/v1/requests/{uuid}
Update the specified Request
update_request_v1 1 param body → 200400401403404429
GET
/v1/requests/{uuid}/sheet-rows
List Sheet Rows that belong to the specified Request
list_sheet_rows_by_request_v1 4 params → 200400401403404429
GET
/v1/requests/{uuid}/files
Fetch the Files for the specified Request
list_request_files_v1 4 params → 200401403404
POST
/v1/requests/{uuid}/files
Upload a File to the specified Request
upload_request_file_v1 1 param body → 200400401403404429
GET
/v1/requests/{uuid}/comments
Fetch the Comments for the specified Request
list_comments_by_request_v1 4 params → 200400401403404429
POST
/v1/requests/{uuid}/comments
Post a Comment on a Request
create_request_comment_v1 1 param body → 201400401403429
POST
/v1/requests/comments
Post Comments on multiple Requests
create_request_comments_v1 body → 201400401403429

Schemas 17

The contract defines 17 schemas that model the data the API accepts and returns. The most detailed are RequestRead (13 properties), FileRead (8 properties), CommentRead (6 properties), ControlRead (4 properties). Each schema is shown below with its type and property counts.

ControlReadLinks
object
1 property 1 required
RequestUpdate
object
1 property
RequestCommentBulkCreate
object
1 property 1 required
HalLink
object
3 properties 2 required
FileRead
object
8 properties 8 required
SheetRowRead
object
3 properties 3 required
SheetReadLinks
object
1 property 1 required
RequestReadLinks
object
1 property 1 required
RequestStatus
string
The request's current status in the evidence-collection workflow.
CommentCreate
object
2 properties 1 required
RequestRead
object
13 properties 13 required
ControlRead
object
4 properties 4 required
FileCreate
object
1 property 1 required
CommentRead
object
6 properties 6 required
RequestCommentBulkCreateItem
object
3 properties 2 required
CommentReadLinks
object
1 property 1 required
FileUploadRead
object
1 property 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

fieldguide-requests-api-openapi.yml Raw ↑

Other APIs Fieldguide publishes across the network.

Fieldguide api API
AE Profile APIs.io
Fieldguide comments API
AE Profile APIs.io
Fieldguide companies API
AE Profile APIs.io
Fieldguide controls API
AE Profile APIs.io
Fieldguide engagements API
AE Profile APIs.io
Fieldguide files API
AE Profile APIs.io
Fieldguide insights API
AE Profile APIs.io
Fieldguide jobs API
AE Profile APIs.io
Fieldguide milestones API
AE Profile APIs.io
Fieldguide sheet-columns API
AE Profile APIs.io
Fieldguide sheet-rows API
AE Profile APIs.io
Fieldguide sheets API
AE Profile APIs.io
#Requests
← Back to F APIs
API Details
ID
fieldguide:fieldguide-requests-api
Base URL
https://api.fieldguide.io
Docs
https://www.fieldguide.io/developers
Provider
Fieldguide
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=fieldguide-requests-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/fieldguide-requests-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of Fieldguide requests API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.