Accounts
JWT token obtained from /api/login/. Pass as: Authorization: Bearer
Items Per Page
Page Number
Sorting Order
Sorting Key
Serializer for Documents.
Recognized primitve fields:
* ``StringField``
* ``URLField``
* ``EmailField``
* ``IntField``
* ``LongField``
* ``FloatField``
* ``DecimalField``
* ``BooleanField``
* ``DateTimeField``
* ``ComplexDateTimeField``
* ``ObjectIdField``
* ``SequenceField`` (assumes it has integer counter)
* ``UUIDField``
* ``GeoPointField``
* ``GeoJsonBaseField`` (all those fields)
* ``DateField``
Compound fields: ListField and DictField are mapped to corresponding DRF fields, with respect to nested field specification.
The ReferenceField is handled like ForeignKey in DRF: there nested serializer autogenerated if serializer depth greater then 0, otherwise it's handled by it's own (results as str(id)).
For EmbeddedDocumentField also nested serializer autogenerated for non-zero depth, otherwise it is skipped. TODO: THIS IS PROBABLY WRONG AND SHOULD BE FIXED.
Generic fields GenericReferenceField and GenericEmbeddedDocumentField are handled by their own with corresponding serializer fields.
Not well supported or untested:
``FileField``
``ImageField``
``BinaryField``
All other fields are mapped to DocumentField and probably will work wrong.
GET /api/account/info/?items_per_page=1&page=1 HTTP/1.1
Host: api.app.projetly.io
Authorization: Bearer YOUR_SECRET_TOKEN
Accept: */*
[
{
"account_id": "text",
"account_name": "text",
"description": "text",
"account_owner": "text",
"linked_projects": "text",
"health_score": "text",
"total_revenue": "text",
"total_projects": "text",
"completed_projects": "text",
"total_deals": "text",
"completed_deals": "text",
"vertical": "text",
"segment": "text",
"website_url": "text",
"region": "text",
"customer": "text",
"is_favourite": true,
"currency_unit": "text",
"logo_path": "text",
"logo": "text",
"insight": {
"ANY_ADDITIONAL_PROPERTY": "anything"
},
"total_formatted_revenue": "text",
"is_internal_account": true,
"company_id": "text"
}
]JWT token obtained from /api/login/. Pass as: Authorization: Bearer
No response body
No content
POST /api/account/info/ HTTP/1.1
Host: api.app.projetly.io
Authorization: Bearer YOUR_SECRET_TOKEN
Content-Type: application/json
Accept: */*
Content-Length: 300
{
"name": "Slack",
"description": "A cloud based team communication platform",
"account_owner": {
"name": "Shyam",
"id": "123"
},
"link_projects": [
{
"project": "Creation of ticket",
"project_id": "PR123"
},
{
"project": "Creation of request",
"project_id": "PR124"
}
],
"health_score": 10,
"total_revenue": 10000,
"logo_path": ""
}No response body
No content
JWT token obtained from /api/login/. Pass as: Authorization: Bearer
Serializer for Documents.
Recognized primitve fields:
* ``StringField``
* ``URLField``
* ``EmailField``
* ``IntField``
* ``LongField``
* ``FloatField``
* ``DecimalField``
* ``BooleanField``
* ``DateTimeField``
* ``ComplexDateTimeField``
* ``ObjectIdField``
* ``SequenceField`` (assumes it has integer counter)
* ``UUIDField``
* ``GeoPointField``
* ``GeoJsonBaseField`` (all those fields)
* ``DateField``
Compound fields: ListField and DictField are mapped to corresponding DRF fields, with respect to nested field specification.
The ReferenceField is handled like ForeignKey in DRF: there nested serializer autogenerated if serializer depth greater then 0, otherwise it's handled by it's own (results as str(id)).
For EmbeddedDocumentField also nested serializer autogenerated for non-zero depth, otherwise it is skipped. TODO: THIS IS PROBABLY WRONG AND SHOULD BE FIXED.
Generic fields GenericReferenceField and GenericEmbeddedDocumentField are handled by their own with corresponding serializer fields.
Not well supported or untested:
``FileField``
``ImageField``
``BinaryField``
All other fields are mapped to DocumentField and probably will work wrong.
GET /api/account/info/{id}/ HTTP/1.1
Host: api.app.projetly.io
Authorization: Bearer YOUR_SECRET_TOKEN
Accept: */*
{
"account_id": "text",
"account_name": "text",
"description": "text",
"account_owner": "text",
"linked_projects": "text",
"health_score": "text",
"total_revenue": "text",
"total_projects": "text",
"completed_projects": "text",
"total_deals": "text",
"completed_deals": "text",
"vertical": "text",
"segment": "text",
"website_url": "text",
"region": "text",
"customer": "text",
"is_favourite": true,
"currency_unit": "text",
"logo_path": "text",
"logo": "text",
"insight": {
"ANY_ADDITIONAL_PROPERTY": "anything"
},
"total_formatted_revenue": "text",
"is_internal_account": true,
"company_id": "text"
}JWT token obtained from /api/login/. Pass as: Authorization: Bearer
No response body
No content
PUT /api/account/info/{id}/ HTTP/1.1
Host: api.app.projetly.io
Authorization: Bearer YOUR_SECRET_TOKEN
Content-Type: application/json
Accept: */*
Content-Length: 90
{
"name": "Slack",
"description": "A cloud based team communication platform for enterprises"
}No response body
No content
JWT token obtained from /api/login/. Pass as: Authorization: Bearer
No response body
No content
DELETE /api/account/info/{id}/ HTTP/1.1
Host: api.app.projetly.io
Authorization: Bearer YOUR_SECRET_TOKEN
Accept: */*
No response body
No content
JWT token obtained from /api/login/. Pass as: Authorization: Bearer
Serializer for Documents.
Recognized primitve fields:
* ``StringField``
* ``URLField``
* ``EmailField``
* ``IntField``
* ``LongField``
* ``FloatField``
* ``DecimalField``
* ``BooleanField``
* ``DateTimeField``
* ``ComplexDateTimeField``
* ``ObjectIdField``
* ``SequenceField`` (assumes it has integer counter)
* ``UUIDField``
* ``GeoPointField``
* ``GeoJsonBaseField`` (all those fields)
* ``DateField``
Compound fields: ListField and DictField are mapped to corresponding DRF fields, with respect to nested field specification.
The ReferenceField is handled like ForeignKey in DRF: there nested serializer autogenerated if serializer depth greater then 0, otherwise it's handled by it's own (results as str(id)).
For EmbeddedDocumentField also nested serializer autogenerated for non-zero depth, otherwise it is skipped. TODO: THIS IS PROBABLY WRONG AND SHOULD BE FIXED.
Generic fields GenericReferenceField and GenericEmbeddedDocumentField are handled by their own with corresponding serializer fields.
Not well supported or untested:
``FileField``
``ImageField``
``BinaryField``
All other fields are mapped to DocumentField and probably will work wrong.
GET /api/account/info/all-accounts/ HTTP/1.1
Host: api.app.projetly.io
Authorization: Bearer YOUR_SECRET_TOKEN
Accept: */*
{
"account_id": "text",
"account_name": "text",
"description": "text",
"account_owner": "text",
"linked_projects": "text",
"health_score": "text",
"total_revenue": "text",
"total_projects": "text",
"completed_projects": "text",
"total_deals": "text",
"completed_deals": "text",
"vertical": "text",
"segment": "text",
"website_url": "text",
"region": "text",
"customer": "text",
"is_favourite": true,
"currency_unit": "text",
"logo_path": "text",
"logo": "text",
"insight": {
"ANY_ADDITIONAL_PROPERTY": "anything"
},
"total_formatted_revenue": "text",
"is_internal_account": true,
"company_id": "text"
}JWT token obtained from /api/login/. Pass as: Authorization: Bearer
Serializer for Documents.
Recognized primitve fields:
* ``StringField``
* ``URLField``
* ``EmailField``
* ``IntField``
* ``LongField``
* ``FloatField``
* ``DecimalField``
* ``BooleanField``
* ``DateTimeField``
* ``ComplexDateTimeField``
* ``ObjectIdField``
* ``SequenceField`` (assumes it has integer counter)
* ``UUIDField``
* ``GeoPointField``
* ``GeoJsonBaseField`` (all those fields)
* ``DateField``
Compound fields: ListField and DictField are mapped to corresponding DRF fields, with respect to nested field specification.
The ReferenceField is handled like ForeignKey in DRF: there nested serializer autogenerated if serializer depth greater then 0, otherwise it's handled by it's own (results as str(id)).
For EmbeddedDocumentField also nested serializer autogenerated for non-zero depth, otherwise it is skipped. TODO: THIS IS PROBABLY WRONG AND SHOULD BE FIXED.
Generic fields GenericReferenceField and GenericEmbeddedDocumentField are handled by their own with corresponding serializer fields.
Not well supported or untested:
``FileField``
``ImageField``
``BinaryField``
All other fields are mapped to DocumentField and probably will work wrong.
Serializer for Documents.
Recognized primitve fields:
* ``StringField``
* ``URLField``
* ``EmailField``
* ``IntField``
* ``LongField``
* ``FloatField``
* ``DecimalField``
* ``BooleanField``
* ``DateTimeField``
* ``ComplexDateTimeField``
* ``ObjectIdField``
* ``SequenceField`` (assumes it has integer counter)
* ``UUIDField``
* ``GeoPointField``
* ``GeoJsonBaseField`` (all those fields)
* ``DateField``
Compound fields: ListField and DictField are mapped to corresponding DRF fields, with respect to nested field specification.
The ReferenceField is handled like ForeignKey in DRF: there nested serializer autogenerated if serializer depth greater then 0, otherwise it's handled by it's own (results as str(id)).
For EmbeddedDocumentField also nested serializer autogenerated for non-zero depth, otherwise it is skipped. TODO: THIS IS PROBABLY WRONG AND SHOULD BE FIXED.
Generic fields GenericReferenceField and GenericEmbeddedDocumentField are handled by their own with corresponding serializer fields.
Not well supported or untested:
``FileField``
``ImageField``
``BinaryField``
All other fields are mapped to DocumentField and probably will work wrong.
POST /api/account/info/del_vertical/ HTTP/1.1
Host: api.app.projetly.io
Authorization: Bearer YOUR_SECRET_TOKEN
Content-Type: application/json
Accept: */*
Content-Length: 252
{
"account_id": "text",
"account_name": "text",
"description": "text",
"vertical": "text",
"segment": "text",
"website_url": "text",
"region": "text",
"is_favourite": true,
"insight": {
"ANY_ADDITIONAL_PROPERTY": "anything"
},
"is_internal_account": true,
"company_id": "text"
}{
"account_id": "text",
"account_name": "text",
"description": "text",
"account_owner": "text",
"linked_projects": "text",
"health_score": "text",
"total_revenue": "text",
"total_projects": "text",
"completed_projects": "text",
"total_deals": "text",
"completed_deals": "text",
"vertical": "text",
"segment": "text",
"website_url": "text",
"region": "text",
"customer": "text",
"is_favourite": true,
"currency_unit": "text",
"logo_path": "text",
"logo": "text",
"insight": {
"ANY_ADDITIONAL_PROPERTY": "anything"
},
"total_formatted_revenue": "text",
"is_internal_account": true,
"company_id": "text"
}JWT token obtained from /api/login/. Pass as: Authorization: Bearer
Serializer for Documents.
Recognized primitve fields:
* ``StringField``
* ``URLField``
* ``EmailField``
* ``IntField``
* ``LongField``
* ``FloatField``
* ``DecimalField``
* ``BooleanField``
* ``DateTimeField``
* ``ComplexDateTimeField``
* ``ObjectIdField``
* ``SequenceField`` (assumes it has integer counter)
* ``UUIDField``
* ``GeoPointField``
* ``GeoJsonBaseField`` (all those fields)
* ``DateField``
Compound fields: ListField and DictField are mapped to corresponding DRF fields, with respect to nested field specification.
The ReferenceField is handled like ForeignKey in DRF: there nested serializer autogenerated if serializer depth greater then 0, otherwise it's handled by it's own (results as str(id)).
For EmbeddedDocumentField also nested serializer autogenerated for non-zero depth, otherwise it is skipped. TODO: THIS IS PROBABLY WRONG AND SHOULD BE FIXED.
Generic fields GenericReferenceField and GenericEmbeddedDocumentField are handled by their own with corresponding serializer fields.
Not well supported or untested:
``FileField``
``ImageField``
``BinaryField``
All other fields are mapped to DocumentField and probably will work wrong.
GET /api/account/info/journey/ HTTP/1.1
Host: api.app.projetly.io
Authorization: Bearer YOUR_SECRET_TOKEN
Accept: */*
{
"account_id": "text",
"account_name": "text",
"description": "text",
"account_owner": "text",
"linked_projects": "text",
"health_score": "text",
"total_revenue": "text",
"total_projects": "text",
"completed_projects": "text",
"total_deals": "text",
"completed_deals": "text",
"vertical": "text",
"segment": "text",
"website_url": "text",
"region": "text",
"customer": "text",
"is_favourite": true,
"currency_unit": "text",
"logo_path": "text",
"logo": "text",
"insight": {
"ANY_ADDITIONAL_PROPERTY": "anything"
},
"total_formatted_revenue": "text",
"is_internal_account": true,
"company_id": "text"
}JWT token obtained from /api/login/. Pass as: Authorization: Bearer
Serializer for Documents.
Recognized primitve fields:
* ``StringField``
* ``URLField``
* ``EmailField``
* ``IntField``
* ``LongField``
* ``FloatField``
* ``DecimalField``
* ``BooleanField``
* ``DateTimeField``
* ``ComplexDateTimeField``
* ``ObjectIdField``
* ``SequenceField`` (assumes it has integer counter)
* ``UUIDField``
* ``GeoPointField``
* ``GeoJsonBaseField`` (all those fields)
* ``DateField``
Compound fields: ListField and DictField are mapped to corresponding DRF fields, with respect to nested field specification.
The ReferenceField is handled like ForeignKey in DRF: there nested serializer autogenerated if serializer depth greater then 0, otherwise it's handled by it's own (results as str(id)).
For EmbeddedDocumentField also nested serializer autogenerated for non-zero depth, otherwise it is skipped. TODO: THIS IS PROBABLY WRONG AND SHOULD BE FIXED.
Generic fields GenericReferenceField and GenericEmbeddedDocumentField are handled by their own with corresponding serializer fields.
Not well supported or untested:
``FileField``
``ImageField``
``BinaryField``
All other fields are mapped to DocumentField and probably will work wrong.
GET /api/account/info/more-activities/ HTTP/1.1
Host: api.app.projetly.io
Authorization: Bearer YOUR_SECRET_TOKEN
Accept: */*
{
"account_id": "text",
"account_name": "text",
"description": "text",
"account_owner": "text",
"linked_projects": "text",
"health_score": "text",
"total_revenue": "text",
"total_projects": "text",
"completed_projects": "text",
"total_deals": "text",
"completed_deals": "text",
"vertical": "text",
"segment": "text",
"website_url": "text",
"region": "text",
"customer": "text",
"is_favourite": true,
"currency_unit": "text",
"logo_path": "text",
"logo": "text",
"insight": {
"ANY_ADDITIONAL_PROPERTY": "anything"
},
"total_formatted_revenue": "text",
"is_internal_account": true,
"company_id": "text"
}JWT token obtained from /api/login/. Pass as: Authorization: Bearer
Serializer for Documents.
Recognized primitve fields:
* ``StringField``
* ``URLField``
* ``EmailField``
* ``IntField``
* ``LongField``
* ``FloatField``
* ``DecimalField``
* ``BooleanField``
* ``DateTimeField``
* ``ComplexDateTimeField``
* ``ObjectIdField``
* ``SequenceField`` (assumes it has integer counter)
* ``UUIDField``
* ``GeoPointField``
* ``GeoJsonBaseField`` (all those fields)
* ``DateField``
Compound fields: ListField and DictField are mapped to corresponding DRF fields, with respect to nested field specification.
The ReferenceField is handled like ForeignKey in DRF: there nested serializer autogenerated if serializer depth greater then 0, otherwise it's handled by it's own (results as str(id)).
For EmbeddedDocumentField also nested serializer autogenerated for non-zero depth, otherwise it is skipped. TODO: THIS IS PROBABLY WRONG AND SHOULD BE FIXED.
Generic fields GenericReferenceField and GenericEmbeddedDocumentField are handled by their own with corresponding serializer fields.
Not well supported or untested:
``FileField``
``ImageField``
``BinaryField``
All other fields are mapped to DocumentField and probably will work wrong.
GET /api/account/info/options/ HTTP/1.1
Host: api.app.projetly.io
Authorization: Bearer YOUR_SECRET_TOKEN
Accept: */*
{
"account_id": "text",
"account_name": "text",
"description": "text",
"account_owner": "text",
"linked_projects": "text",
"health_score": "text",
"total_revenue": "text",
"total_projects": "text",
"completed_projects": "text",
"total_deals": "text",
"completed_deals": "text",
"vertical": "text",
"segment": "text",
"website_url": "text",
"region": "text",
"customer": "text",
"is_favourite": true,
"currency_unit": "text",
"logo_path": "text",
"logo": "text",
"insight": {
"ANY_ADDITIONAL_PROPERTY": "anything"
},
"total_formatted_revenue": "text",
"is_internal_account": true,
"company_id": "text"
}JWT token obtained from /api/login/. Pass as: Authorization: Bearer
^[^/]+$Serializer for Documents.
Recognized primitve fields:
* ``StringField``
* ``URLField``
* ``EmailField``
* ``IntField``
* ``LongField``
* ``FloatField``
* ``DecimalField``
* ``BooleanField``
* ``DateTimeField``
* ``ComplexDateTimeField``
* ``ObjectIdField``
* ``SequenceField`` (assumes it has integer counter)
* ``UUIDField``
* ``GeoPointField``
* ``GeoJsonBaseField`` (all those fields)
* ``DateField``
Compound fields: ListField and DictField are mapped to corresponding DRF fields, with respect to nested field specification.
The ReferenceField is handled like ForeignKey in DRF: there nested serializer autogenerated if serializer depth greater then 0, otherwise it's handled by it's own (results as str(id)).
For EmbeddedDocumentField also nested serializer autogenerated for non-zero depth, otherwise it is skipped. TODO: THIS IS PROBABLY WRONG AND SHOULD BE FIXED.
Generic fields GenericReferenceField and GenericEmbeddedDocumentField are handled by their own with corresponding serializer fields.
Not well supported or untested:
``FileField``
``ImageField``
``BinaryField``
All other fields are mapped to DocumentField and probably will work wrong.
GET /api/account/info/overview/{id}/ HTTP/1.1
Host: api.app.projetly.io
Authorization: Bearer YOUR_SECRET_TOKEN
Accept: */*
{
"account_id": "text",
"account_name": "text",
"description": "text",
"account_owner": "text",
"linked_projects": "text",
"health_score": "text",
"total_revenue": "text",
"total_projects": "text",
"completed_projects": "text",
"total_deals": "text",
"completed_deals": "text",
"vertical": "text",
"segment": "text",
"website_url": "text",
"region": "text",
"customer": "text",
"is_favourite": true,
"currency_unit": "text",
"logo_path": "text",
"logo": "text",
"insight": {
"ANY_ADDITIONAL_PROPERTY": "anything"
},
"total_formatted_revenue": "text",
"is_internal_account": true,
"company_id": "text"
}JWT token obtained from /api/login/. Pass as: Authorization: Bearer
Serializer for Documents.
Recognized primitve fields:
* ``StringField``
* ``URLField``
* ``EmailField``
* ``IntField``
* ``LongField``
* ``FloatField``
* ``DecimalField``
* ``BooleanField``
* ``DateTimeField``
* ``ComplexDateTimeField``
* ``ObjectIdField``
* ``SequenceField`` (assumes it has integer counter)
* ``UUIDField``
* ``GeoPointField``
* ``GeoJsonBaseField`` (all those fields)
* ``DateField``
Compound fields: ListField and DictField are mapped to corresponding DRF fields, with respect to nested field specification.
The ReferenceField is handled like ForeignKey in DRF: there nested serializer autogenerated if serializer depth greater then 0, otherwise it's handled by it's own (results as str(id)).
For EmbeddedDocumentField also nested serializer autogenerated for non-zero depth, otherwise it is skipped. TODO: THIS IS PROBABLY WRONG AND SHOULD BE FIXED.
Generic fields GenericReferenceField and GenericEmbeddedDocumentField are handled by their own with corresponding serializer fields.
Not well supported or untested:
``FileField``
``ImageField``
``BinaryField``
All other fields are mapped to DocumentField and probably will work wrong.
Serializer for Documents.
Recognized primitve fields:
* ``StringField``
* ``URLField``
* ``EmailField``
* ``IntField``
* ``LongField``
* ``FloatField``
* ``DecimalField``
* ``BooleanField``
* ``DateTimeField``
* ``ComplexDateTimeField``
* ``ObjectIdField``
* ``SequenceField`` (assumes it has integer counter)
* ``UUIDField``
* ``GeoPointField``
* ``GeoJsonBaseField`` (all those fields)
* ``DateField``
Compound fields: ListField and DictField are mapped to corresponding DRF fields, with respect to nested field specification.
The ReferenceField is handled like ForeignKey in DRF: there nested serializer autogenerated if serializer depth greater then 0, otherwise it's handled by it's own (results as str(id)).
For EmbeddedDocumentField also nested serializer autogenerated for non-zero depth, otherwise it is skipped. TODO: THIS IS PROBABLY WRONG AND SHOULD BE FIXED.
Generic fields GenericReferenceField and GenericEmbeddedDocumentField are handled by their own with corresponding serializer fields.
Not well supported or untested:
``FileField``
``ImageField``
``BinaryField``
All other fields are mapped to DocumentField and probably will work wrong.
POST /api/account/info/vertical/ HTTP/1.1
Host: api.app.projetly.io
Authorization: Bearer YOUR_SECRET_TOKEN
Content-Type: application/json
Accept: */*
Content-Length: 252
{
"account_id": "text",
"account_name": "text",
"description": "text",
"vertical": "text",
"segment": "text",
"website_url": "text",
"region": "text",
"is_favourite": true,
"insight": {
"ANY_ADDITIONAL_PROPERTY": "anything"
},
"is_internal_account": true,
"company_id": "text"
}{
"account_id": "text",
"account_name": "text",
"description": "text",
"account_owner": "text",
"linked_projects": "text",
"health_score": "text",
"total_revenue": "text",
"total_projects": "text",
"completed_projects": "text",
"total_deals": "text",
"completed_deals": "text",
"vertical": "text",
"segment": "text",
"website_url": "text",
"region": "text",
"customer": "text",
"is_favourite": true,
"currency_unit": "text",
"logo_path": "text",
"logo": "text",
"insight": {
"ANY_ADDITIONAL_PROPERTY": "anything"
},
"total_formatted_revenue": "text",
"is_internal_account": true,
"company_id": "text"
}Last updated