Mavenlink Project Templates API
Project Templates are sets of tasks and attributes that can be applied to new or existing projects.A single template can be used on any number of projects.A project template's tasks are all stored in an attribute located on the project template object called raw_json.It is a JSON hash of all the stories that has been turned into a string and is stored on the object.##### Project Template Stories (Tasks) - raw_jsonA project template's tasks are all stored in an attribute located on the project template object called raw_json.It is a JSON hash of all the stories that has been turned into a string and is stored on the object.Stories within the JSON have the following attributes: * `title` - The title of the task. * `billable` - The title of the project template. * `relative_start_date` - An integer that represents the start day of the task relative to the startof the project. * `relative_due_date` - An integer that represents the end day of the task relative to the startof the project. * `duration` - The number of days the task will take to complete. * `temp_id` - The unique reference ID for the task (used for dependencies). * `description` - The task description. * `budget_estimate_in_cents` - An integer (whole number) that represents the budget estimate, incents, for the task. * `time_estimate_in_minutes` - An integer (whole number) that represents the time estimate, in minutes,for the task. * `sub_stories` - An nested array of sub-tasks that have the same structure as tasks. * `checklist` - An array of strings, each being a checklist item on the task. For example, "checklist":["item one", "item two"]. * `tag_list` - A string with tags that are comma separated. For example, "design, engineering, this has spaces." This creates three tags: "design", "engineering", and "this has spaces." * `assignments` - An array of objects with key value pairs "assignee_id":id. For example, [{"assignee_id":100},{"assignee_id":101}] This task would have two resources assigned to it. These are the IDs of two associated project templateassignments. Project template assignments are associated objects. * `dependencies` - An array of objects that represent a task's dependencies. A dependency is an object that connects two tasks, and is used in Gantt charts. A dependency objectlives in the dependencies array on it's source task, not it's target.Dependencies have the following attributes: * `source_id` - The temporary ID of the first task (source task) in the dependency. * `target_id` - The temporary ID of the second task (target task) in the dependency. * `type` - There are four types of dependencies, numbered zero through three. * 0 - From the beginning of the source task to the beginning of the target task. * 1 - From the beginning of the source task to the end of the target task. * 2 - From the end of the source task to beginning of the target task. * 3 - From the end of the source task to end of the target task. * `lag` - An integer that represents the number of days delay that occurs between the two tasksin the dependency.raw_json example:```[ { "story_type":"task", "billable":true, "relative_start_date":1, "relative_due_date":2, "title":"Task One", "temp_id":1, "dependencies":[{"source_id":1, "target_id":2, "type":2, "lag":0}], "description":"this is a task", "assignments":[{"assignee_id":"26"}], "tag_list":"difficult,easy", "budget_estimate_in_cents":40000, "time_estimate_in_minutes":1200, "sub_stories": [ { "story_type":"task", "billable":true, "due_date":nil, "start_date":nil, "relative_start_date":1, "relative_due_date":3, "title":"Sub Task One", "description":"this is a sub task", "assignments":[{"assignee_id":"27"}], "budget_estimate_in_cents":20000, "time_estimate_in_minutes":300, "temp_id":3 } ] }, { "story_type":"deliverable", "billable":true, "endDay":4, "relative_start_date":1, "relative_due_date":4, "title":"Deliverable One", "temp_id":2, "description":"this is a deliverable", "sub_stories":[] }, { "story_type":"milestone", "billable":true, "title":"Milestone One", "description":"this is a milestone", "weight":100, "duration":0, "relative_start_date":5, "sub_stories":[], "checklist":["item one", "item two"], "temp_id":4 }]```.
Mavenlink Project Templates API is one of 103 APIs that Mavenlink publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Project Templates. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, authentication docs, and rate-limit docs.
This API exposes 5 operations across 2 paths, and defines 6 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.
Requests are made against a single base URL, https://api.mavenlink.com/api/v1.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 2
Mavenlink Project Templates API declares
2 security schemes
for authenticating requests.
An API key is passed in the header as Bearer (BearerToken).
It supports OAuth 2.0 (OauthSecurity) using the authorizationCode flow.
Paths & Operations 5
Across 2 paths, the API surfaces 5 operations — 1 DELETE, 2 GET, 1 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.
Project Templates are sets of tasks and attributes that can be applied to new or existing projects. A single template can be used on any number of projects. A project template's t…
Schemas 6
The contract defines 6 schemas that model the data the API accepts and returns. The most detailed are User (20 properties), ProjectTemplate (16 properties), ProjectTemplateAssignment (7 properties), ProjectTemplateAdditionalTab (3 properties). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from Mavenlink 12
Other APIs Mavenlink publishes across the network.
This is an independent, third-party profile of Mavenlink Project Templates 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.