<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>thread Invoices API - add reference_id and metadata to Invoice object in Archived Discussions (Read Only)</title>
    <link>https://community.squareup.com/t5/Archived-Discussions-Read-Only/Invoices-API-add-reference-id-and-metadata-to-Invoice-object/m-p/259924#M96831</link>
    <description>&lt;P&gt;Hey there,&lt;BR /&gt;&lt;BR /&gt;I'm developing for a customer an advanced airtable invoicing app that generates square invoices from airtable data.&lt;BR /&gt;&lt;BR /&gt;I noticed that the &lt;A href="https://developer.squareup.com/reference/square/objects/Invoice" target="_blank" rel="noopener"&gt;Invoice object&lt;/A&gt; is missing the standard reference_id and metadata fields that do exist in the Order object. This will force me to do an order get in my webhooks to figure out the airtable record ID I should update with the invoice changes, since I do store this in the order the invoice was generated for.&lt;BR /&gt;&lt;BR /&gt;In general I think that any API object, not only the Invoice object, should have those fields for easy synchronization and integration with external systems.&lt;BR /&gt;&lt;BR /&gt;Cheers,&lt;/P&gt;</description>
    <pubDate>Thu, 01 Apr 2021 00:01:47 GMT</pubDate>
    <dc:creator>rbabayoff</dc:creator>
    <dc:date>2021-04-01T00:01:47Z</dc:date>
    <item>
      <title>Invoices API - add reference_id and metadata to Invoice object</title>
      <link>https://community.squareup.com/t5/Archived-Discussions-Read-Only/Invoices-API-add-reference-id-and-metadata-to-Invoice-object/m-p/259924#M96831</link>
      <description>&lt;P&gt;Hey there,&lt;BR /&gt;&lt;BR /&gt;I'm developing for a customer an advanced airtable invoicing app that generates square invoices from airtable data.&lt;BR /&gt;&lt;BR /&gt;I noticed that the &lt;A href="https://developer.squareup.com/reference/square/objects/Invoice" target="_blank" rel="noopener"&gt;Invoice object&lt;/A&gt; is missing the standard reference_id and metadata fields that do exist in the Order object. This will force me to do an order get in my webhooks to figure out the airtable record ID I should update with the invoice changes, since I do store this in the order the invoice was generated for.&lt;BR /&gt;&lt;BR /&gt;In general I think that any API object, not only the Invoice object, should have those fields for easy synchronization and integration with external systems.&lt;BR /&gt;&lt;BR /&gt;Cheers,&lt;/P&gt;</description>
      <pubDate>Thu, 01 Apr 2021 00:01:47 GMT</pubDate>
      <guid>https://community.squareup.com/t5/Archived-Discussions-Read-Only/Invoices-API-add-reference-id-and-metadata-to-Invoice-object/m-p/259924#M96831</guid>
      <dc:creator>rbabayoff</dc:creator>
      <dc:date>2021-04-01T00:01:47Z</dc:date>
    </item>
    <item>
      <title>Re: Invoices API - add reference_id and metadata to Invoice object</title>
      <link>https://community.squareup.com/t5/Archived-Discussions-Read-Only/Invoices-API-add-reference-id-and-metadata-to-Invoice-object/m-p/260436#M96832</link>
      <description>&lt;P&gt;Hey hello &lt;a href="https://community.squareup.com/t5/user/viewprofilepage/user-id/362681"&gt;@rbabayoff&lt;/a&gt;! Welcome to our Seller Community, and thanks for posting.&amp;nbsp;&lt;/P&gt;

&lt;P&gt;&amp;nbsp;&lt;/P&gt;

&lt;P&gt;Certainly appreciate the feedback here. I went ahead and shared it with our API teams so they can look into this a bit more. If anything else comes up please let us know. Happy to have you here!&lt;/P&gt;</description>
      <pubDate>Fri, 02 Apr 2021 18:36:03 GMT</pubDate>
      <guid>https://community.squareup.com/t5/Archived-Discussions-Read-Only/Invoices-API-add-reference-id-and-metadata-to-Invoice-object/m-p/260436#M96832</guid>
      <dc:creator>nika</dc:creator>
      <dc:date>2021-04-02T18:36:03Z</dc:date>
    </item>
  </channel>
</rss>

