Curl create ticket, missing signature

  • Used Zammad version: 3.1.x
  • Used Zammad installation source: Debian-Sourcelist (by Zammad)
  • Operating system: Debian 9
  • Browser + version: Chromium 75.0.3770.100, Firefox 68.0.1

Expected behavior:

  • That an automatic e-mail WITH signature is sent via the CURL command.

Actual behavior:

  • The e-mail is sent WITHOUT a signature.
  • Only logged in to Zammad, the signature of the group is automatically added to the user as soon as he creates an e-mail and selects the greetings.

Steps to reproduce the behavior:

  • Use this CURL-Command.

    curl -s --cacert /etc/ssl/certs/cacert.pem
    -H “Authorization: Token token=XXX”
    -H “Content-Type: application/json”
    -X POST -d ‘{“title”: “XXX”, “group”:“First-Level::Second-Level”,“state_id”: 1,“customer”:"’$customer_mail’",“article”:{“content_type”:“text/html”,“origin”:“XXX”,“to”:"’$customer_mail’",“subject”: “XXX”,“body”: "XXX ‘$lname’,“type”: “email”,“internal”: false},“note”:“vServer Install”}’ \https://XXX/api/v1/tickets

No Idea? I need your Help! :slight_smile:

As far as I understand the source code, Zammads WebApp actually is in charge for adding the signature.
Meaning: Zammads API already gets the content with Signature which is why it doesn’t need to add it later on.

I personally would see issues in changing that.

@thorsteneckel might correct me here though.

@MrGeneration is right. The Signature is added by the frontend WebApp and gives the user the freedom to remove or change it at any point. You could fetch the signatures via the signature API endpoint and add it to your text in your calling script.

Great. We missed that part of the API. Where exactly is it documented? :slight_smile:

Our API documentation is not that advanced yet. But it should be pretty straight forward when looking at the code:

Hope that helps :slight_smile:

This topic was automatically closed 120 days after the last reply. New replies are no longer allowed.