Skip to main content
POST
/
memos
/
{id}
/
approve
curl -X POST https://api.companyflow.com/memos/550e8400-e29b-41d4-a716-446655440000/approve \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "comments": "Approved - looks good to proceed"
  }'

{
  "success": true,
  "data": {
    "id": "550e8400-e29b-41d4-a716-446655440000",
    "company_id": "123e4567-e89b-12d3-a456-426614174000",
    "created_by": "987e6543-e21b-12d3-a456-426614174000",
    "memo_type": "policy",
    "title": "Updated Remote Work Policy",
    "content": "Effective immediately, all employees are eligible for hybrid work arrangements...",
    "reference_number": "MEMO-2025-001",
    "priority": "high",
    "status": "approved",
    "current_step": 2,
    "approved_by": "abc12345-e89b-12d3-a456-426614174000",
    "approved_at": "2025-03-03T15:30:00Z",
    "created_at": "2025-03-03T10:00:00Z",
    "updated_at": "2025-03-03T15:30:00Z"
  }
}

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/Falasefemi2/companyflow/llms.txt

Use this file to discover all available pages before exploring further.

Approve a memo at its current workflow approval step. This moves the memo forward in the approval chain or marks it as fully approved if this is the final step.

​
Authentication

Requires authentication with Bearer token. Available to:
  • Manager
  • HR Manager
  • Super Admin
Only users with approval authority at the current workflow step can approve the memo. Employees without manager privileges cannot access this endpoint.

​
Path Parameters

​
id
string
required
The unique identifier of the memo (UUID format)Example: "550e8400-e29b-41d4-a716-446655440000"

​
Request Body

​
comments
string
Optional approval comments or notesExample: "Approved - looks good to proceed"

​
Response

​
success
boolean
Indicates if the request was successful
​
data
object
The updated memo object with new approval status
curl -X POST https://api.companyflow.com/memos/550e8400-e29b-41d4-a716-446655440000/approve \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "comments": "Approved - looks good to proceed"
  }'

{
  "success": true,
  "data": {
    "id": "550e8400-e29b-41d4-a716-446655440000",
    "company_id": "123e4567-e89b-12d3-a456-426614174000",
    "created_by": "987e6543-e21b-12d3-a456-426614174000",
    "memo_type": "policy",
    "title": "Updated Remote Work Policy",
    "content": "Effective immediately, all employees are eligible for hybrid work arrangements...",
    "reference_number": "MEMO-2025-001",
    "priority": "high",
    "status": "approved",
    "current_step": 2,
    "approved_by": "abc12345-e89b-12d3-a456-426614174000",
    "approved_at": "2025-03-03T15:30:00Z",
    "created_at": "2025-03-03T10:00:00Z",
    "updated_at": "2025-03-03T15:30:00Z"
  }
}

​
Approval Workflow

1

Memo Creation

A memo is created with status draft or pending
2

Workflow Steps

The memo moves through approval steps defined in the workflow configuration
3

Manager Approval

Authorized managers approve at each step using this endpoint
4

Final Status

After all approvals, the memo status becomes approved and is visible to all recipients

​
Authorization Rules

Who can approve:
  • The memo must be at a workflow step where the current user has approval authority
  • Managers can typically approve memos from their direct reports or department
  • HR Managers and Super Admins can approve any memo
  • The approval authority is determined by the workflow configuration
Include meaningful comments when approving to provide context for the memo creator and other stakeholders in the approval chain.

Build docs developers (and LLMs) love

Get started for freeTalk to us