Lap Agentos Api V3 Diary Call Group

agentOS API V3, Diary Call Group API skill. Use when working with agentOS API V3, Diary Call Group for diary. Covers 13 endpoints.

Security Scan

The skill's requirements and runtime instructions are consistent with a simple API integration for the agentOS Diary Call Group; nothing requested or instructed appears disproportionate to that purpose.

Purpose & Capability

Name/description match the actions in SKILL.md: it documents 13 diary-related endpoints and only requests a single API key (AGENTOS_API_V3_DIARY_CALL_GROUP_API_KEY) which is exactly what an API client would need. The source/homepage are missing (unknown publisher), so verify provenance if that matters to you.

Instruction Scope

SKILL.md confines runtime behavior to calling the documented endpoints, setting the API key in request headers, and using LAP tooling (npx @lap-platform/lapsh) to refresh/search the spec. It does not instruct reading unrelated files, extra environment variables, or transmitting data to unexpected endpoints beyond the documented base URL (https://live-api.letmc.com).

Install Mechanism

No install spec and no code files — instruction-only. This minimizes disk writes and arbitrary code execution risk.

Credentials

Only one env var is required and it is clearly named for the API key used by this integration. No unrelated secrets, config paths, or broad credential requests are present.

Persistence & Privilege

always is false and the skill does not request system-wide changes or access to other skills' configs. disable-model-invocation is false (normal autonomous invocation default) and does not combine with any other red flags here.

Assessment

This skill appears to be a straightforward client spec for the agentOS Diary Call Group API and is internally consistent. Before installing: 1) Confirm you trust the publisher (no homepage/source provided). 2) Ensure the AGENTOS_API_V3_DIARY_CALL_GROUP_API_KEY you provide has the minimum privileges needed and is stored securely. 3) Verify the base URL (https://live-api.letmc.com) is the intended service for your organization. 4) Note the SKILL.md references references/api-spec.lap and uses npx @lap-platform/lapsh — if you run those commands the agent/environment will make network requests to fetch specs; test with non-production credentials first. 5) Because this is instruction-only, it won't drop code on disk, but the agent will make outbound requests to the API when used — review data sent to the API if it contains sensitive information.

agentOS API V3, Diary Call Group

API version: v3-diary

Auth

basic | ApiKey ApiKey in header

Base URL

https://live-api.letmc.com

Setup

1. Set your API key in the appropriate header
2. GET /v3/diary/{shortname}/{branchID}/guest/search -- verify access
3. POST /v3/diary/{shortName}/appointment -- create first appointment

Endpoints

13 endpoints across 1 groups. See references/api-spec.lap for full details.

diary

Method	Path	Description
GET	/v3/diary/{shortname}/{branchID}/guest/search	Match Guest Parameters with existing applicants
GET	/v3/diary/{shortName}/allocations	Get a list of all available allocations for a date + 7 days for a specified appointment type
GET	/v3/diary/{shortName}/appointment	Get an appointment by ID
PUT	/v3/diary/{shortName}/appointment	Update an existing appointment using its unique identifier
POST	/v3/diary/{shortName}/appointment	Post an appointment into a valid diary allocation
DELETE	/v3/diary/{shortName}/appointment	Delete an existing appointment using its unique identifier
PATCH	/v3/diary/{shortName}/appointment/{appointmentID}/cancel	Cancel an existing appointment using its unique identifier
POST	/v3/diary/{shortName}/appointment/feedback	Submit appointment feedback
GET	/v3/diary/{shortName}/appointmentsbetweendates	A collection of diary appointments linked to a company filtered between specific dates and by appointment type
GET	/v3/diary/{shortName}/appointmenttypes	A collection of all diary appointment types
GET	/v3/diary/{shortName}/company/branches	All branches defined for a company
GET	/v3/diary/{shortName}/company/branches/{branchID}	Get a specific branch given its unique Object ID (OID)
GET	/v3/diary/{shortName}/recurringappointment	Retrieves all recurring appointments:-

Common Questions

Match user requests to endpoints in references/api-spec.lap. Key patterns:

• "List all search?" -> GET /v3/diary/{shortname}/{branchID}/guest/search
• "List all allocations?" -> GET /v3/diary/{shortName}/allocations
• "List all appointment?" -> GET /v3/diary/{shortName}/appointment
• "Create a appointment?" -> POST /v3/diary/{shortName}/appointment
• "Create a feedback?" -> POST /v3/diary/{shortName}/appointment/feedback
• "List all appointmentsbetweendates?" -> GET /v3/diary/{shortName}/appointmentsbetweendates
• "List all appointmenttypes?" -> GET /v3/diary/{shortName}/appointmenttypes
• "List all branches?" -> GET /v3/diary/{shortName}/company/branches
• "Get branche details?" -> GET /v3/diary/{shortName}/company/branches/{branchID}
• "List all recurringappointment?" -> GET /v3/diary/{shortName}/recurringappointment
• "How to authenticate?" -> See Auth section

Response Tips

• Check response schemas in references/api-spec.lap for field details
• List endpoints may support pagination; check for limit, offset, or cursor params
• Create/update endpoints typically return the created/updated object

CLI

# Update this spec to the latest version
npx @lap-platform/lapsh get agentos-api-v3-diary-call-group -o references/api-spec.lap

# Search for related APIs
npx @lap-platform/lapsh search agentos-api-v3-diary-call-group

References

• Full spec: See references/api-spec.lap for complete endpoint details, parameter tables, and response schemas

Generated from the official API spec by LAP